RFR: 8302618: [macos] Problem typing uppercase letters with java.awt.Robot when moving mouse [v9]

[Harshitha Onkar]

On Thu, 6 Jun 2024 19:38:46 GMT, BlakeTNC <duke at openjdk.org> wrote:

>> Harshitha Onkar has updated the pull request incrementally with one additional commit since the last revision:
>> 
>>   changed allModifiersMask datatype
>
> Hello, I am the developer that originally reported this bug to the Adoptium team. I was reviewing the bug discussions on this page and elsewhere, and I have a suggestion and some questions.
> 
> ### Did Apple fix this bug? (It still does not work for me on the latest macOS.)
> 
> I read this comment:
>> Link: https://bugs.openjdk.org/browse/JDK-8302618
>> Harshitha Onkar added a comment - 2023-12-22 14:45
>> [~prr] Revisited this issue. It works fine on the latest macOS 14.2 and still fails on macOS 
>> Ventura. This is true for the Java test case and the native reproducer.
>> Something must have been fixed on the new version although there wasn't any update on the 
>> Apple Bug report that was filed. 
> 
> I tested the bug today and I am still able to replicate it on my own computer, using the following set up: An M1 Macbook Pro running Sonoma 14.5, on JDK 19 and JDK 22 (Zulu 22.0.1+8). So, it appears that Apple might not have fixed this issue in the latest MacOS.
> 
> ### Suggestion, Add unit tests for this bug to the openJDK:
> It appears that this pull request includes some test code for this issue. I would suggest, at minimum, that unit testing for this issue be added to the openJDK. That way if the Robot functionality breaks in any future versions of macOS (or other operating systems), it will be caught more quickly by the openJDK developers. Apparently this issue existed for years without anyone noticing. It would be sad for the same issue to resurface in the future, without anyone noticing again. 
> 
> Note that unit tests for this issue could be added to the JDK regardless of whether any bug fix is applied in openJDK, using conditional test execution. If there is an express decision to NOT fix this issue in the JDK (and to instead rely on a fix that was or will be supplied by Apple), then if desired, the testing code could be surrounded with a conditional code block to exclude only the past version(s) of macOS that are known to be broken. That way the tests would only execute, 1) On all the existing and past operating system versions where Robot is currently known or expected to work correctly, and 2) On all future operating system releases.
> 
> ### Option, Apply a bug fix in the openJDK, since Apple has not explicitly responded:
> 
> It may be useful to apply a fix for this bug in the openJDK, (if there is no detriment to doing so), rather than relying solely on any fix that Apple may (or may not) release. Based on Harshitha Onkar's comment copied above, I have an impression that ...

@BlakeTNC I was able to reproduce this issue again on macOS 14.5. Currently I'm looking into this PR and revisiting all the previous discussions. I'll have an update for all the posted questions soon. Thanks!

> PS, There is an Apple Developer forum post here: (https://forums.developer.apple.com/forums/thread/733161) where someone tried to report this issue to Apple on that forum. In the same thread, Apple suggested reporting the issue using a different channel called the Apple Feedback Assistant. Apparently that is an official channel for reporting Apple bugs.
> Feedback Assistant instructions page: https://developer.apple.com/bug-reporting/
> Feedback Assistant link: https://feedbackassistant.apple.com/

That Dev Forum post was posted by me and additionally filed a bug report through Feedback Assistant at that time.

> Something must have been fixed on the new version (14.2) although there wasn't any update on the
> Apple Bug report that was filed.

The bug report I was referring to was the Feedback Assistant report here.

>  I could send a report to Apple myself, but I may not be the best person to file the report. I would have trouble giving them all the needed information because I am not familiar with the topics of Objective-C, the CGEventSourceFlagsState API, or the event flags that have been mentioned as potentially being at the root of the issue.

I can file a new Feedback Assistant report again (against macOS 14.5) on your behalf and check if they provide any updates or solution this time. Additionally I'll check if I can file a Technical Support Incident (TSI) with Apple, but the developer account seems to be down currently for maintenance. https://developer.apple.com/maintenance/

@BlakeTNC Submitted Feedback Assistant Bug report again (against macOS 14.5)

-------------

PR Comment: https://git.openjdk.org/jdk/pull/14744#issuecomment-2157299195
PR Comment: https://git.openjdk.org/jdk/pull/14744#issuecomment-2158815301
PR Comment: https://git.openjdk.org/jdk/pull/14744#issuecomment-2164399878