This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 219315

Summary: DOM breakpoints not being detected for a momment after running file
Product: javascript Reporter: Vladimir Riha <vriha>
Component: DebuggerAssignee: Martin Entlicher <mentlicher>
Status: NEW ---    
Severity: normal CC: vriha
Priority: P3    
Version: 7.3   
Hardware: PC   
OS: Linux   
Issue Type: DEFECT Exception Reporter:

Description Vladimir Riha 2012-10-02 09:15:04 UTC 
When I run HTML file, Navigator window displays message "DOM has changed" and it seems that DOM breakpoints are not detected (are ignored) as long as this message is displayed. Once the message is hidden, DOM breakpoints work as charm. Might be some coincidence but if not, user should be at least informed somehow about this delay (at least in "New Breakpoint" dialog or somewhere else)


Product Version: NetBeans IDE 7.3 Beta (Build 201210011125)
Java: 1.7.0_07; Java HotSpot(TM) Client VM 23.3-b01
System: Linux version 3.2.0-31-generic-pae running on i386; UTF-8; en_US (nb)
Comment 1 Vladimir Riha 2013-01-07 15:27:19 UTC 
The message was probably removed but the issue is still here. As a side effect, you can't use DOM breakpoints on elements that are modified on document load. For instance:

$(document).ready(function() {
 for (var prop in menuList) {
        if (menuList.hasOwnProperty(prop)) {
            $("#menu").append("<li>A</li>");
        }
    }
});

Then if you use DOM breakpoint (subtree modifications) on #menu element, the breakpoint is not being hit


Product Version: NetBeans IDE Dev (Build web-main-9643-on-20130106)
Java: 1.7.0_10; Java HotSpot(TM) Client VM 23.6-b04
Runtime: Java(TM) SE Runtime Environment 1.7.0_10-b18
System: Linux version 3.2.0-35-generic-pae running on i386; UTF-8; en_US (nb)