On Sun, 6 Sep 2026 15:18:36 GMT, Thiago Milczarek Sayao <[email protected]> wrote:
>> 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. I fixed the issue where programmatically resizing a non-resizable window was not working correctly. Since the previous implementation was re-adding the constraints with the old values, size changes were not being propagated to Java, which caused the test to pass even though the behavior was incorrect. It is possible for the test to pass in scenarios where Java is not notified that the resize was rejected. One way to make the test more robust would be to take a snapshot of the Scene and verify its actual size, but I’m not sure if that would be a good approach for a test. ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/2139#discussion_r3944670520
