JDK-8350504 : When closing a full-screen window a portion of the overlay can be seen
  • Type: Bug
  • Component: javafx
  • Sub-Component: window-toolkit
  • Affected Version: internal
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: os_x
  • Submitted: 2025-02-21
  • Updated: 2025-08-06
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.
Other
internalUnresolved
Related Reports
Causes :  
Description
After the glass refactoring in JDK-8325379, a portion of the full-screen overlay window is transiently visible in the lower right of the window as it is animating from full screen size to normal size before it closes. See the attached screen shot.

To reproduce this bug, run the following on macOS from a local build of the metal sandbox branch:

1. java -cp apps/toys/Hello/dist/Hello.jar hello.HelloFullscreen
2. Quickly (before the overlay banner disappears) click on the "Close" button.
3. BUG: after the window has animated from full-screen to normal size, and before the window actually closes, you will see a portion of the overlay in the lower right of the window.

This reproduces on all pipelines (MTL, ES2, SW) after the glass refactoring.
Comments
You might be right about this being due to a change in timing. I ran this against mainline using the ES2 pipeline, and out of about 40 runs it failed twice for me. As such, I'll lower this to P4.
24-02-2025

This issue is not reproducible in my M1 16inch Macbook pro with macOS 14.7.1 and Ajit's Intel 16inch Macbook pro with discrete AMD GPU. This issue is reproducible in Ambarish's Intel integrated SoC 14inch Macbook pro with macOS 14.7.1. Also this issue happens 1/5 times in jfx mainline with ES2 pipeline on same Ambarish's machine. Looks like refactoring under JDK-8325379 has converted this from intermittent to always issue on some specific machines.
24-02-2025