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.
Created attachment 124019 [details] webkit log To reproduce: - use sampleApp from our wiki - open in IDE and run debugger.html file - add DOM breakpoints to <li> items between lines 66 to 77 (type is described at the list item) - add DOM breakpoint for subtree modifications for <ul> on line 68 Now in browser (Chrome), start Select Mode and hover over the <ul> element => some code execution is stopped (Continue button becomes green) and all interactions with the page is paused. You need to press Continue twice to make it work (at least until next hover over the <ul>...) When this happens, the code execution does not stop at any of my source line and call stack window shows 1 rectangle with no text, tooltip text says ":126" Product Version: NetBeans IDE Dev (Build 201209070001) Java: 1.7.0_07; Java HotSpot(TM) Client VM 23.3-b01 System: Linux version 3.2.0-29-generic-pae running on i386; UTF-8; en_US (nb)
Created attachment 124021 [details] IDE log (In reply to comment #0) > Now in browser (Chrome), start Select Mode and hover over the <ul> element Please note that all hovering is done in browser not Navigator. By <ul> I mean area in browser where this element is (Reproducible with clean user dir)
This is because implementation of Select Mode changes DOM and therefore the DOM breakpoint is hit. This will be always a tricky problem. For NB 7.3 I would be actually tempted to leave it almost as it is. We could try to filter out "internal DOM" changes but I'm not sure that's a good approach. I would rather communicate to users that DOM debugging and document styling are two mutually exclusive operations.
I see what you mean and agree it is 2 different things. Would it be possible to deactivate all breakpoints when select mode is enabled? And then reactivate them back once you disable select mode? If at the time of enabling Select Mode code execution was stopped on some breakpoint, Continue action would be done and then all breakpoints deactivated. The point is that it is not always clear that "now you only debugging" and "now you only styling". You can find some css issue while debugging and decide to fix it and vice versa. Anyway, this is probably should be more like P3. If you think the ideas above makes no sense or are not worth it, I would agree with WONTFIX
(In reply to comment #3) > Would it be possible to deactivate all breakpoints when select mode is enabled? This does sound to me like a good idea.