Issue metadata
Sign in to add a comment
|
Focus events come in the wrong order when using Docs spelling dialog |
||||||||||||||||||||||||
Issue descriptionActivate Jaws 18 and Chrome 60+. Create a Google doc with a few misspelled words. Activate the spell checker. Activate the Change button to replace a word. When the suggestion for the next word is shown, use Insert+Up (or CapsLock+Up if in laptop layout) to read the current line. Actual result: Notice that the current line that is being read is the line in the document where the misspelling is present. Expected result: The line that is being read should be the suggested word in the spelling dialog. Cause: Two focus events are raised by Chrome + Docs. One tells Jaws to focus the line in the document where the misspelling is present and the second to focus the suggestion back in the spelling dialog. The events come in the wrong order. Focusing the document to read the misspelling in context might be fine, if right after that the suggestion was focused. However, it seems that the event for focusing the document comes after the event for focusing the dialog.
,
Aug 4 2017
,
Aug 4 2017
,
Aug 8 2017
I did some debugging today and it seems the bug doesn't reproduce any more.
I monitored the focus, blur and other events for the document content editable and the spelling suggestion input using the following commands in Chrome Dev Tools:
monitorEvents($("#docs-spellcheckslidingdialog-replacement-input"), "control");
monitorEvents($(".docs-texteventtarget-iframe"), "control");
Steps:
I typed a document with two spelling mistakes. I opened the spelling dialog and at the first suggestion I pressed "Change". I waited for the second misspelling to be identified and pressed JawsKey+Up. The suggestion was read as expected.
In the console, I only got a blur event from the document which is a bit strange because I was also expecting a focus event from the spelling suggestion input.
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by grotival@google.com
, Jun 9 2017