On Mon, 1 Jun 2026 15:56:04 GMT, Alexander Zvegintsev <[email protected]> wrote:
> JDK-8185862 did not try to exclude all virtual displays. It filtered out > monitors that AWT cannot use: `EnumDisplayMonitors` may report a monitor, but > `CreateDC` fails for it. Why AWT cannot use that displays? If a simple native UI application starts on that system, will it fail to create frames/windows as well for example "calc"? Why, in that mode, instead of the values returned by CreateDC, cannot AWT use some fallback values? > 1. [`Session > 0`](https://techcommunity.microsoft.com/blog/askperf/application-compatibility---session-0-isolation/372361), > when AWT application launched as a windows service. It should be detected as > headless. > 2. Display transitional states, such as when an RDP connection is established. It should work in a similar way the native UI applications work, this sequence of patches breaks people for no reason. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/31238#discussion_r3338131313
