New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 600146 link

Starred by 1 user
Status: Duplicate
Merged: issue 689195
Owner:
█ nek...@chromium.org
Last visit > 30 days ago
Closed: Dec 2017
Cc:
dmazz...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

[a11y] Backspace doesn't speak in contentEditables (e.g. message body in Inbox or GMail)

Reported by kevincha...@gmail.com, Apr 2 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2695.1 Safari/537.36

Steps to reproduce the problem:
1. Install/run NVDA from http://www.nvaccess.org/
2. inbox.google.com
3. C to Create new message > tab to message body > type text > BACKSPACE to delete text

What is the expected behavior?
Deleted text to be reported by NVDA

What went wrong?
No feedback when pressing BACKSPACE

Did this work before? No 

Chrome version: 51.0.2695.1  Channel: canary
OS Version: Windows 10
Flash Version: Shockwave Flash 21.0 r0

Comment 1 by nimerjaber1@gmail.com, Apr 2 2016 

I have found this to be inconsistent at best. Sometimes, backspace press reads out the letter erased, and sometimes it doesn't. When it does, it only reads out a letter or two, and then goes silent for a letter or two.

Comment 2 by durga.behera@chromium.org, Apr 6 2016

Cc: dmazz...@chromium.org
Components: -UI UI>Accessibility
Labels: M-51
Owner: dtseng@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Win 10 using 49.0.2623.110 and canary 51.0.2701.0.
Was able to narrow bisect manually as below.
Good :45.0.2436.0
Bad : 45.0.2446.0
Note : Due to network slowness for sometime was unable to proceed further.
Omahaproxy UI Cl:
https://chromium.googlesource.com/chromium/src/+log/45.0.2436.0..45.0.2446.0?pretty=fuller&n=10000

suspect : https://codereview.chromium.org/1213513003
dtseng@ : Could you please take a look into this if its related to your change.

While tried to bisect with the tool in one of the build the pages were were blank and considered it as Bad revision and continued for bisect.But the CL did not produce any suspect.
Change Log:
https://chromium.googlesource.com/chromium/src/+log/13c5c463e5ac7e561b4d3d919010d7b206509f5e..a1d0e3255b40fb17d0c1da33ed7566fc8f6cf819
-----------

Comment 3 by nek...@chromium.org, Apr 6 2016

Owner: nek...@chromium.org
This is more related to the changes with content editable I made, so I am taking it on.

Comment 4 by nek...@chromium.org, Nov 14 2016

Status: Available (was: Assigned)
It seems that the bug only occurs when you press backspace quickly after the previous keypress, e.g. if you are pressing backspace repeatedly. Jaws 18 doesn't exhibit the same bug.

Comment 5 by chaok@google.com, Dec 16 2016

Labels: -Pri-2 Pri-1

Comment 6 by dmazz...@chromium.org, Mar 27 2017

Labels: NewComponent-Accessibility NewComponent-Accessibility-Compatibility

Comment 7 by dmazz...@chromium.org, Apr 21 2017

Components: UI>Accessibility>Compatibility

Comment 8 by dmazz...@chromium.org, Apr 21 2017

Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility

Comment 9 by dmazz...@chromium.org, Aug 4 2017

Labels: triage-dougt

Comment 10 by dougt@chromium.org, Aug 4 2017

Labels: -triage-dougt
Status: ExternalDependency (was: Available)
Bug with NVDA and not with JAWS per comment #4.  Marking ExternalDependency

Comment 11 by nek...@chromium.org, Dec 11 2017

Mergedinto: 689195
Status: Duplicate (was: ExternalDependency)

Comment 12 by leberly@chromium.org, Jan 17 2018

Labels: win-a11y
►

Sign in to add a comment