On Mon, 10 Jun 2024 11:29:10 GMT, BlakeTNC <[email protected]> wrote: >> Harshitha Onkar has updated the pull request incrementally with one >> additional commit since the last revision: >> >> changed allModifiersMask datatype > > 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/ > > It is unclear to me if anyone has reported the bug using the Apple Feedback > Assistant. 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.
@BlakeTNC Thank you for your patience. Please find the answers below. > Did Apple fix this bug? (It still does not work for me on the latest macOS.) This issue is reproducible on macOS 14.5 although it did seem to work on macOS 14.2. Along with Feedback Assistant report, a Technical Support Incident was raised. Received a reply from Apple - we are in the discussion stage, so it might take sometime to understand different scenarios and formulate a solution that works well in all cases. > 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 Apple has not yet responded to this issue. I also learned > today that macOS Ventura is the last macOS system that many older Mac models > can run. That is because > reportedly[[1]](https://www.techradar.com/computing/mac-os/the-latest-macos-ventura-update-has-left-owners-of-old-macs-stranded-in-a-sea-of-problems-raising-a-chorus-of-complaints) > [[2]](https://en.wikipedia.org/wiki/MacOS_Sonoma#Supported_hardware), macOS > Sonoma only supports Mac computer models from 2018 onwards. So if this bug is > not fixed in the JDK, then it will likely never be fixed for many older Mac > models. Also as I mentioned above, this bug still exist for me even though I > am currently running macOS Sonoma 14.5. If I understand correctly, that means > it's possible that Apple has not fixed the problem for the latest versions of macOS. The proposed fix in this PR works well only in some cases. More details documented here https://github.com/openjdk/jdk/pull/14744#issuecomment-1662976048. So adding the proposed fix can cause unexpected results in other cases. Since this scenario is reproducible with a native reproducer too (using Apple APIs), it is important to understand if it needs to be fixed on their end or is this an inherent API behavior before proceeding with a solution. Now that we have received a reply from Apple, this scenario and native API working can be discussed in depth. ------------- PR Comment: https://git.openjdk.org/jdk/pull/14744#issuecomment-2183543951
