RFR: 8372415: Stage size should match visual window bounds [v3]

[Michael Strauß]

On Wed, 17 Dec 2025 19:28:05 GMT, Martin Fox <mfox at openjdk.org> wrote:

>> If we removed that path, then for Windows 10 < 1607, we wouldn't be able to skip coordinate mapping for the usual (99.9%) case when the Java process is running with per-monitor DPI awareness. This wouldn't cause JavaFX to stop working, we'd just be back at the status quo where we don't account for the visible window frame.
>> 
>> We still need to dynamically load the function though, as it definitely won't be available on Win10 < 1607.
>
>> We still need to dynamically load the function though, as it definitely won't be available on Win10 < 1607.
> 
> Officially you're doing the right thing by writing code that works on all versions of Windows 10. But this assumes there are users out there with the original release of Windows 10 (no updates past 2015) who will want to install a JavaFX 26-based app. Are there? Can we even test this code? I don't see how this is sustainable going forward.
> 
> This is not really a question for you. I should take it to the mailing list.

I can't test this in a systematic way, as I can't be bothered to get an installation of an ancient version of Windows. However, in this particular case, I _did_ test what would happen if the new functions can't be loaded by simply commenting out the code that loads the new functions.

-------------

PR Review Comment: https://git.openjdk.org/jfx/pull/1982#discussion_r2628418795