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.
In the easel_css_72 build 55, with the NetBeans plugin for Chrome/Firefox installed: 1. Create a Java SE project 2. In the main class, write some imports of Java SE classes 3. Call code completion inside the import statement - cc window and Javadoc window will be opened 4. In the doc window toolbar, click the "Show documentation in external web browser" icon. 5. Javadoc will be opened in the external browser tab; repeat steps 3 and 4 with another import statement The same browser tab as before will be reused - I would expect that a new browser tab will be opened - this was also the previous behavior. Next, previously the browser window was fronted as I opened the external browser, currently the browser window is not fronted and NetBeans remains fronted, which is also a usability problem.
Previous behavior was not necessarily better than current one. In my experience, at the end of the day, I often end up with dozen or two of tabs opened from each project execution which I had to close one by one. We should think what's desirable and what not. In this case you just keep opening documentation so a single tab is better response I would think. Question is whether sharing the same tab with unrelated actions make sense or not: eg. run project versus generate documentation. Second issue is giving browser a focus after document reload - not sure whether that's possible to do or not.
web-main#d13550b5ebc8
Integrated into 'main-golden', will be available in build *201209031048* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/d13550b5ebc8 User: Denis Anisimov <ads@netbeans.org> Log: Fix for BZ#208576 - New browser tab should always be used for non-webapp-related actions and BZ#209358 - Browser plugin installation should not be offered for non-webapp use cases