On Wed, 30 Apr 2025 21:26:41 GMT, Kevin Rushforth wrote:
> During the headful test run, the following test failed on all four of our
> test systems, so it is likely related to your fix.
I think it's unrelated. During testing @andy-goryachev-oracle noted that the
demaximized position test was n
On Wed, 30 Apr 2025 03:38:34 GMT, Martin Fox wrote:
>> On macOS the system animates the transition into and out of fullscreen and
>> this animation runs asynchronously. JavaFX tries to make the setFullScreen
>> call appear synchronous by running a nested event loop while the transition
>> is g
On Wed, 30 Apr 2025 03:38:34 GMT, Martin Fox wrote:
>> On macOS the system animates the transition into and out of fullscreen and
>> this animation runs asynchronously. JavaFX tries to make the setFullScreen
>> call appear synchronous by running a nested event loop while the transition
>> is g
On Wed, 30 Apr 2025 03:38:34 GMT, Martin Fox wrote:
>> On macOS the system animates the transition into and out of fullscreen and
>> this animation runs asynchronously. JavaFX tries to make the setFullScreen
>> call appear synchronous by running a nested event loop while the transition
>> is g
> On macOS the system animates the transition into and out of fullscreen and
> this animation runs asynchronously. JavaFX tries to make the setFullScreen
> call appear synchronous by running a nested event loop while the transition
> is going on. But this means that runLater runnables can fire d
