On Tue, 10 Jun 2025 22:23:32 GMT, Alexey Ivanov <aiva...@openjdk.org> wrote:
>> 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? Since the standalone test works as expected on windows, I'm not sure if we need to problemlist it on windows, as @aivanov-jdk mentioned earlier it must a side-effect of PFJ. I used the standalone test and added another dummy frame, even with extra frame the test works as expected. (cursor remains a I-beam until the left mouse btn is released) ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/25705#discussion_r2141174989
