RFR: 8315986: javax/swing/JMenuItem/4654927/bug4654927.java: component must be showing on the screen to determine its location [v2]
Harshitha Onkar
honkar at openjdk.org
Fri Oct 6 04:56:01 UTC 2023
On Wed, 4 Oct 2023 08:32:31 GMT, Prasanta Sadhukhan <psadhukhan at openjdk.org> wrote:
>> Can you please tell which system it is not working?
>> I guess harshita and vitaly tested on macos14 and it worked for them and I tested on other mac13,windows10 locally where it also worked, as well as in mach5 systems, whose link I have put in JBS.
>>
>> I also have seen the menu disappear while clicking but it does not cause the test to fail..I saw the video recording vitaly uploaded in JBS and it is same as in macos13 where it pass always (we also dont see any failure for this test in CI runs so far)
>
> Add a delay to make it work on mach5 mac14 system. Tested for 50 iterations, link in JBS
@prsadhuk
> These don't help on the system I have tested on. There's something else going on. The test is basically about verifying that clicking on a disabled menu item doesn't dismiss the menu. I don't think it does. If I comment out the press/release the same exception occurs. And visually you can see the menu disappear and then reappear. What it looks like is that the call at line 86/91 to mouseMove which returns the pointer to the "menu" location causes the list of menu items to disappear and then quickly reappear. Sampling if the menu is on screen at that time will cause the error. It only happens once .. very odd ..
Ran the updated test MacOS 14 ARM, thought the test passes there seems to be an issue similar to what Phil described earlier - the menu appears then disappears and appears again quickly for the second scenario - when the menu is clicked and glided through the dropdown. I have attached the screen recording to the JBS.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/15677#discussion_r1348241212
More information about the client-libs-dev
mailing list