JDK-8163101 : dual-screen issue with JMenu, JPopupMenu
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 9
  • Priority: P3
  • Status: Closed
  • Resolution: Cannot Reproduce
  • Submitted: 2016-08-03
  • Updated: 2017-01-23
  • Resolved: 2017-01-23
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9Resolved
Related Reports
Duplicate :  
JDK-8160270 - dual-screen issue with java.awt.Choice
Relates :  
JDK-8137571 - Linux HiDPI Graphics support
Relates :  
JDK-8160270 - dual-screen issue with java.awt.Choice
Description
Ubuntu 16.04 Linux + JDK9b130 (client nightly) + two displays (HiDPI, but not sure if it does matter).

Please run the test case from JDK-8163100 on display  #1 and move the window to the display #2. Try to open the menu - it will appear somewhere on the displ. #1. The same for popup menu.


quite similar to JDK-8160270 (probably a duplicate)
Comments
I tried to reproduce this issue on dual monitor virtualbox screen on ubuntu16.04 with fresh checked-out[19/1] jdk9 workspace. One monitor resolution is 1600x1200 and another monitor resolution is 2560x1600. I tried with "scale for menu & titlebars" value of 1 and 2. When I move the IconTest window from monitor 1 to monitor 2 and click on "test" menu, it opens up the menu in monitor 2 in both scale cases, and not in monitor 1 as bug report mentioned. So, I think it's not reproducible anymore.
19-01-2017
http://mail.openjdk.java.net/pipermail/awt-dev/2016-September/012007.html Take a look to the logic in JPopupMenu.adjustPopupLocationToFitScreen and related methods.
07-11-2016
Re-assigned to JDK-8137571 owner
07-11-2016
please see also JDK-8159968. probably the same issue (forgot about this bug filed earlier) - but it's FX-related.
05-08-2016