On Sun, 6 Sep 2026 12:42:16 GMT, Thiago Milczarek Sayao <[email protected]>
wrote:
>> tests/system/src/test/java/test/javafx/stage/StageSizingTest.java line 511:
>>
>>> 509: runAndWait(() -> {
>>> 510: getStage().setWidth(NEW_WIDTH);
>>> 511: getStage().setHeight(NEW_HEIGHT);
>>
>> `Window.setWidth()` and `Window.setHeight()` update the Java properties
>> immediately, before native confirmation. If GTK rejects the resize without
>> emitting a configure event, the Java property assertions can still report
>> the requested values while the native window remains at the old size.
>
> I took this into consideration. The native side will notify the Java side if
> the resize cannot be applied, so the Java properties will be updated
> accordingly. Since this notification is asynchronous, there's a delay before
> checking the values.
You’re right. The test does pass despite the issue mentioned in the other
comment about using the old min/max values, because in this case the Java side
is not notified. I think the solution would be to have a Robot test take a
screenshot and measure the actual window size.
-------------
PR Review Comment: https://git.openjdk.org/jfx/pull/2139#discussion_r3944393325
