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.
As of Chrome 27 (released a few days ago), it is possible to turn off the debugging infobar saying "NetBeans Connector is debugging this tab". To do that, the user needs to: 1. Go to chrome://flags/ in Chrome 2. Enable the "Enable Silent Debugging" flag 3. Restart Chrome (See bug https://code.google.com/p/chromium/issues/detail?id=138258 filed by the NetBeans team for background.) We should provide guidance/instructions to the user to do this, so she can do this permanently and save vertical space. I doubt we can enable silent debugging automatically on user's behalf, but at least we should alert the user about this possibility at the appropriate occasion - probably whenever she closes the infobar? Or at some other time as well?
*** Bug 226951 has been marked as a duplicate of this bug. ***
From Liza's e-mail: The more I think about it, the more I think we should simply alert the user when she manually closes the yellow message by reworking the existing message slightly as follows. We should do nothing when the user toggles to CDT by selecting Chrome's inspect option. NetBeans Connector has Closed // big title next to warning icon. Note I'm being very specific about wording to avoid saying that NB has "disconnected" from Chrome To run the NetBeans Connector without the debugging infobar, select the Enable Silent Debugging flag in Chrome. // message in bold It looks like you closed the debugging infobar by clicking its Cancel button or Close icon. Unless you enable silent debugging, Chrome requires that this remain open while working with the NetBeans extension. Note: although the NetBeans Connector has closed, changes in Chrome and NetBeans are still synchronized. Learn more... // detail message. Can we add a link to help here? Keep the screenshot and OK button as they are.
Done, please verify it if possible. Two notes: - waiting for Ken for the documentation, - unfortunately, IMHO we cannot find out why we were disconnected so we are showing the warning dialog even if the cause is CDT - Honzo, do you have any idea whether it is possible? Thanks. http://hg.netbeans.org/web-main/rev/f7eddac6eaaa
> - unfortunately, IMHO we cannot find out why we were disconnected so we are > showing the warning dialog even if the cause is CDT - Honzo, do you have any > idea whether it is possible? It seems that they have added this information into the debugger API some time ago. See the commit: http://git.chromium.org/gitweb/?p=git/chromium.git;a=commitdiff;h=60473c7698700f53917eb7b60b09206ff2f4fec5 the api (the second parameter of onDetach): http://developer.chrome.com/extensions/debugger.html#event-onDetach
Integrated into 'main-golden', will be available in build *201306112301* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/f7eddac6eaaa User: Tomas Mysik <tmysik@netbeans.org> Log: #230292 - Provide guidance on hiding the yellow infobar permanently
(In reply to comment #4) > the api (the second parameter of onDetach): > http://developer.chrome.com/extensions/debugger.html#event-onDetach Thanks a lot Honzo! However, it does not work for me in 100 % but only sometimes. Thanks. http://hg.netbeans.org/web-main/rev/97389bbdc99f
Integrated into 'main-golden', will be available in build *201306122301* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/97389bbdc99f User: Tomas Mysik <tmysik@netbeans.org> Log: #230292 cont'd - Provide guidance on hiding the yellow infobar permanently Reason for debugger detaching added.