On Tue, 10 Jun 2025 21:23:42 GMT, Damon Nguyen <dngu...@openjdk.org> wrote:
>> I guess it's not the first time that we've encountered such an issue where >> using `PassFailJFrame` changes the behaviour of the test. Was it >> @TejeshR13's test? >> >> I'm confused because `PassFailJFrame` does nothing more than provides a >> standard UI. It uses Swing components to display UI. Could this affect AWT >> components? >> >> We have to look into what may cause the differences in behaviour. > > I have been looking at it and fiddling with the standalone > (non-PassFailJFrame) test to see if I can re-create the behavior without > `PassFailJFrame`. I suspected AWT components being the issue but I can't see > why. > > I tried using EventQueue and SwingUtilities `invokeAndWait()` method to see > if either made a difference, but to no success. I tried different layouts for > the frame but I got the same result. I'll keep looking but I may also append > `windows` to the ProblemList temporarily if I cannot find the source in a > reasonable amount of time. Could it be that mere existence of other windows created by the same Java process somehow changes the cursors? I mean `PassFailJFrame` displays another window. What if you create a second window (that may display nothing inside) in your stand-alone test? Does it change what cursors you see when dragging? ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/25705#discussion_r2138860812
