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.
Steps * Make sure Auto Popup Documentation Window is on * Check Display Documentation Popup Next to Compleiton * Invokde code completion Expected result: * Javadoc window is displayed next (left or right) to the completion window Actual result: * Javadoc window continues to be displayed above the completion window.
Created attachment 154901 [details] Shows the issue Product Version: NetBeans IDE 8.1 Beta (Build 201507231027) Java: 1.8.0_60-ea; Java HotSpot(TM) 64-Bit Server VM 25.60-b23 Runtime: Java(TM) SE Runtime Environment 1.8.0_60-ea-b25 System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb) User directory: C:\Users\markiewb\AppData\Roaming\NetBeans\8.1beta Cache directory: C:\Users\markiewb\AppData\Local\NetBeans\Cache\8.1beta
Created attachment 154929 [details] Works for me Strange because it works OK for me. I have tried with several different IDE positions and sizes. Product Version: NetBeans IDE 8.1 Beta (Build 201507231027) Java: 1.8.0_60-ea; Java HotSpot(TM) 64-Bit Server VM 25.60-b23 Runtime: Java(TM) SE Runtime Environment 1.8.0_60-ea-b25 System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb) User directory: C:\Users\cendrowiczm\AppData\Roaming\NetBeans\8.1beta Cache directory: C:\Users\cendrowiczm\AppData\Local\NetBeans\Cache\8.1beta
Unfortunately, I cannot reproduce the issue.
I can reproduce it. It happens to me when the cursor is at the bottom part of the editor (which is at the bottom of the screen) so the documentation window won't match into the space between cursor position and the bottom of the screen.
I believe this happens when there isn't enough space in the IDE window to fit both Suggestion and JavaDoc window. For the first screenshot of the issue attached, as we can see there isn't enough space (particularly height height) to place the documentation window next to the suggestion window. I investigated this issue from different scenarios, and I think NB is functioning correctly.