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.
Build: NetBeans IDE Dev (Build web-main-9389-on-20121130) VM: Java HotSpot(TM) 64-Bit Server VM, 23.6-b04, Java(TM) SE Runtime Environment, 1.7.0_10-ea-b15 OS: Mac OS X User Comments: pjiricka: I believe it was: 1. Created the BackboneWineCellar sample HTML5 project 2. Close index.html 3. Run it in Chrome 4. Enable select mode and select "2009 Syrah Washington, USA" 5. In the popup menu of the selected node in navigator, select Go to Source Stacktrace: java.lang.AssertionError at org.netbeans.modules.web.webkit.debugging.TransportHelper.sendBlockingCommand(TransportHelper.java:113) at org.netbeans.modules.web.webkit.debugging.api.Runtime.evaluate(Runtime.java:117) at org.netbeans.modules.web.inspect.webkit.WebKitPageModel.invokeInAllDocuments(WebKitPageModel.java:662) at org.netbeans.modules.web.inspect.webkit.WebKitPageModel$WebPaneSynchronizer.updateSelection(WebKitPageModel.java:887) at org.netbeans.modules.web.inspect.webkit.WebKitPageModel$WebPaneSynchronizer.updateSelection(WebKitPageModel.java:881) at org.netbeans.modules.web.inspect.webkit.WebKitPageModel$WebPaneSynchronizer.updateSelection(WebKitPageModel.java:877)
Created attachment 128647 [details] stacktrace
Now happens to me after every keystroke in index.html => P2.
Created attachment 128651 [details] stacktrace To reproduce: - run some html file in Chrome - start Inspect Mode (note that Navigator contains some dynamic elements) - left click on ANY element in Navigator
Created attachment 128656 [details] stacktrace
this IMO belongs to web.inspect as web.inspect.webkit.WebKitPageModel$WebPaneSynchronizer.updateSelection() calls the TransportHelper.sendBlockingCommand() in EDT.
This is a regression caused by http://hg.netbeans.org/web-main/rev/e433cf9cd71b Honzo B., what was the reason for this change? Could you, please, revert it, i.e., stop calling Page.setSelectedNodes() in event-dispatch thread. I understand that you overlooked that because the assertion is thrown when the Select Mode is turned on in the browser only. I should probably add another assertion into setSelectedNodes() directly to catch this kind of problems immediately.
I have reverted the mentioned change. Honzo B., please, let me know if there was some strong reason for it. If so, then we will have to resolve it in a different way. Thank you in advance. Modified file: http://hg.netbeans.org/web-main/rev/f5d91a212f18
Thanks and sorry. There is some minor issue with selection, which needs to be resolved.