Issue metadata
Sign in to add a comment
|
ChromeVox doesn't respect typing echo settings in Gmail editor
Reported by
st...@sawczyn.com,
Oct 9 2016
|
||||||||||||||||||||||||
Issue descriptionI have ChromeVox set to echo words when typing. This setting seems to hold in most web forms, but not the Gmail editor. In Gmail, parts of words are spoken as I type not just as words are completed. To replicate: 1. open Gmail and compose a new message. 2. Set typing echo to words by pressing ChromeVox a followed by t. 3. Begin typing the body of the message. Despite the setting, you will hear portions of words being spoken as you type. Mode: force_next Version: 55.0.2878.0 Reproduction Steps: 1. 2. 3.
,
Oct 16 2016
Hmm, an interesting idea, but what's announced is the partial words that I type. The setting seems to work fine on web pages, just not the Google editor. As I write this comment, I opened another window to a Google Doc and find that in there, characters are always echoed regardless of how echo is set. I realize that's another issue, but the common denominator, at least for now, are the Google rich editors.
,
Oct 22 2016
The control is a content editable, which other richtext editors use as well.
,
Oct 24 2016
FYI; this is a blink level issue. Typing rapidly triggers text selection changes on more than the character (e.g. typing "test" fast, we get one event for the text change "test"). Note that this occurred in Classic as well and was work around by implementing key echo (which is different than character echo).
,
Dec 5 2016
,
Mar 6 2017
,
Mar 27 2017
,
Apr 21 2017
,
Apr 21 2017
,
Aug 10 2017
,
Aug 10 2017
I believe this issue has been fixed since the move over to rich text editing. Please speak up if you still see this issue.
,
Jan 22 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by chaok@google.com
, Oct 16 2016