Issue metadata
Sign in to add a comment
|
Inconsistent verbalizations in VoiceOver for input boxes depending on length of content |
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: 1. Turn on Voice Over 2. Open one of the following fiddles and tab back and forth between the fields: FIDDLE A: https://jsfiddle.net/x7kdtuhe/ FIDDLE B: https://jsfiddle.net/d5ko11ek/ What is the expected behavior? Tabbing back and forth should verbalize the content of the newly focused text box. What went wrong? FIDDLE A verbalizes A, B, A, B when tabbing back and forth FIDDLE B continually verbalizes BB when tabbing back from BB to AA Did this work before? N/A Chrome version: 59.0.3071.115 Channel: n/a OS Version: OS X 10.12.6 Flash Version:
,
Sep 15 2017
Tested on Chrome Stable#61.0.3163.91, Canary#63.0.3216.0 on Mac 10.12.6 and able to reproduce the issue. Please find the bisect info below: Chrome Good Build - 51.0.2673.0 (380313) Chrome Bad Build - 51.0.2678.0 (380962) Note: There are no builds available for Mac between 51.0.2673.0 and 51.0.2678.0. Per-revision bisect didn’t work as the Good build and Bad build fall under M-51 and hasbisect provided all good builds. Hence couldn’t find the possible suspect through script and providing details manually. Below is the CL: https://chromium.googlesource.com/chromium/src/+log/51.0.2673.0..51.0.2678.0?pretty=fuller&n=10000 https://chromium.googlesource.com/skia.git/+/b4ecabd5a2c359f66a20207ffb02a77e624560c4 From the CL above, assigning to the possible susplect. @ericrk -- Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to owner concerned. Thanks.
,
Jan 18 2018
This is unrelated to my chnange. ellyjones@, over to you for Mac Accessability. Apologies if you're not the right person for this - if so, can you help reassign.
,
Jan 18 2018
Laura, can you reproduce on the latest Stable and Canary? I tried and I'm not seeing the issue.
,
Jan 19 2018
I can reproduce this on 65.0.3325.0. With VoiceOver captions turned on (VO Utility > Visuals > Panels and Menus > Show caption panel), I see that what happens is this: "A Insertion at end of text, Box 1, edit text" [hit VoiceOver next field key] "Bb selected" [hit VoiceOver previous field key] "A Insertion at end of text, Box 1, edit text" "Bb unselected" but the "Bb unselected" happens *immediately* after the "A Insertion..." happens, so to a user using VoiceOver with only sound, the apparent behavior is as in the original report. I think this has to do with us sending the events in the wrong order, perhaps? nektar@ might be a good person to investigate this.
,
Apr 23 2018
macOS High Sierra version 10.13.4 with VoiceOver 8 (562.18.4) Google Chrome 68.0.3401.0 (Official Build) canary (64-bit) Unable to rero, resolving as WontFix, it was likely fixed during our other improvements since January. Steps followed: # Turn on Voice Over (with captions for convenience if needed) # Open one of the following fiddles and tab back and forth between the fields: FIDDLE A: https://jsfiddle.net/x7kdtuhe/ FIDDLE B: https://jsfiddle.net/d5ko11ek/ Actual: Tabbing back and forth verbalizes the content of the newly focused text box. It says "A Insertion at end of text, Box 1, edit text" and "B Insertion at end of text, Box 2, edit text" as expected on the first, then on the second fiddle the letter is said properly and text is selected, you are able to insert characters at the end, etc. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by erikc...@chromium.org
, Aug 9 2017Components: Blink>Accessibility