On Mon, 25 Aug 2025 10:43:51 GMT, Anass Baya <[email protected]> wrote:
>> **Analysis :**
>> When the problem occurrs, the key press event related to the mnemonic
>> triggers the item selection. However, as we returned to the menu, the
>> subsequent key typed event arrived and was treated as a normal key press
>> instead of being recognized as part of the mnemonic sequence.
>>
>> **Proposed Fix:**
>> As a fix, we are tagging the next key typed event to be consumed by the
>> Keyboard Focus Manager
>>
>>
>> public void processKeyEvent(Component focusedComponent, KeyEvent e) {
>> // consume processed event if needed
>> if (consumeProcessedKeyEvent(e)) { <--- consumed here
>> return;
>> }
>> ...
>
> Anass Baya has updated the pull request incrementally with one additional
> commit since the last revision:
>
> add Linux bug ID 8321303
I have rebuilt the changes on my other macOS device. It seems to work. To check
again, I ran CI with and without the changes, and windows DOES fail without the
changes in CI (and others pass regardless). I'm inclined to say this passes now
and that it was a host issue on my side for my other device.
-------------
Marked as reviewed by dnguyen (Committer).
PR Review: https://git.openjdk.org/jdk/pull/26790#pullrequestreview-3258706336
