UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
1. Type a word incorrectly "tset" for example
2. Put the cursor on the word
3a. Press the menu key on a keyboard, rapidly followed by the key 'a'
4a. If timed correctly, the word will get replaced with "a", and the spelling corrections menu will show up. Selecting a correction will not do anything

3b. Press the menu key on a keyboard, rapidly followed by the right arrow key
4b. If timed correctly, the cursor will move to the end of the word and the spelling corrections menu will show up. Selecting a correction will not do anything

The timing on this is quite precise, so it may take several tries. 

What is the expected behavior?
Any input after pressing the menu key should be applied to the menu. An example of this is selecting an option in the context menu. When rapidly pressing an arrow key after hitting the context menu button, an option in the context menu should be selected.

What went wrong?
It seems something is going wrong in the order of queuing input. Any input done after the menu key is pressed will be applied to the text, but after the menu has already opened. As the menu selects the full word, this may move the cursor to the end of the word, or replace the selected word with the input. 

Did this work before? N/A 

Chrome version: 62.0.3202.94  Channel: stable
OS Version: 10.0
Flash Version: 

This bug has been observed in multiple Chromium programs: Slack, Atom, and Chrome. While trying to record it using the tool ScreenToGif I was unable to reproduce it in 15/15 tries, versus being able to produce it about 1/4 times when not recording.
 

Deleted: bug.mp4 3.1 MB

	bug.mp4 3.1 MB View Download