<AWT Dev> RFR: 8256465: [macos11] Java frame and dialog presented full screen freeze application

Sergey Bylokhov serb at openjdk.java.net
Sat Apr 10 20:30:28 UTC 2021

On Sat, 10 Apr 2021 16:50:15 GMT, Kevin Rushforth <kcr at openjdk.org> wrote:

> There is a larger issue here than just a freeze in full-screen mode. A user can set their "Prefer tabs" preference for opening documents to "Always" (rather than the default "in full screen") on either 10.15 or 11.0, and then all top level windows will open up in a tab unless they are child (owned) windows.

Yes, I have tested that.

> This leads to a variety of unexpected behavior, which is why I think disabling it (as we did for JavaFX and as is proposed in this PR) is the best option. An application's windows are not always conceptually a set of related documents, so opening up all windows in tabs seems wrong.

All above are applicable to any applications and all frames/dialogs on the new macOS. For some reason, Apple decided this can be a good design. Why we do not try to fit in it? 
 - We may try to configure the correct size when a few windows are merged to the same window
 - We may try to fix a "hang" of some type of the windows
 - And we may try to disable it for some type of the windows by creating "fake" owner.


PR: https://git.openjdk.java.net/jdk/pull/3407

More information about the awt-dev mailing list