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 138073 [details] chrome netbeans connector bug with chrome inspector Hi, I downloaded today the 7.4 build 201307302300 and installed it, I used the chrome-netbeans-connector_v1.0.10.crx given in its installation folder, I opened a project and run it with chrome integration, all was fine till I opened the chrome inspector and tried to run the same script from netbeans, then a critical message told me that I have "to close chrome inspector" in order to reload the page, a restriction that wasn't in the previous version of this extension v1.0.9. Please see the attachment Any help please
This restriction has always been here, even in 7.3 you cannot use NetBeans' inspection features if Chrome Developer Tools (CDT) are open because there could be only 1 debugging session for page: either CDT or NetBeans Inspection. In previous builds, this dialog wasn't present. So if you ran project when CDT is open in Chrome, NetBeans Inspection also didn't work with previous builds. So now there is an explanation to tell users what to do to make NetBeans inspection working again. So now simply close CDT and then run project and it should be OK. See issue 233496 for more details. Thank you for reporting
Thank you for your reactivity. What I discovered just now, is that the page is reloaded in the browser even if the warring message is displayed! Thank you again
Yes, Chrome Developer Tools are better supported since NB 7.4. User gets two choices: #1) do not use CDT and rely fully on NetBeans tooling #2) use CDT tooling and let NB to persist changes done in CDT (and vice versa: changes done in NB are automatically reloaded in CDT/Chrome)