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

Issue 912689 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

When setting textarea value behavior of chrome+mac voiceover doesn't match other browsers.

Reported by amirjan...@gmail.com, Dec 6

Issue description

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

Steps to reproduce the problem:
1. open the attached html file
2. enable voiceover on mac
3. focus on the textarea
4. press a keyboard key (e.g. shift or arrowKey)
javascript will change the value of textarea to a value containing the name of the key

What is the expected behavior?
On safari with mac voiceover, and on chrome on windows with nvda, the new value of textarea  is announced  (or the line where the cursor is located, if the value is multiline)

What went wrong?
On chrome with mac voiceover the old value of textarea is announced, then the new value is read character by character

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 70.0.3538.110  Channel: n/a
OS Version: 
Flash Version: 

this issue affects ace (https://ace.c9.io/) and monaco (https://microsoft.github.io/monaco-editor/) code editors which modify the value of the textarea when selection is moved between lines
 
accessibility.html
91 bytes View Download
Components: Blink>Accessibility
Labels: -Pri-2 -Via-Wizard-API Target-73 M-73 Pri-1
Owner: nek...@chromium.org
Status: Assigned (was: Unconfirmed)
Mac triage: I can repro this locally. The first time I tried I actually got a crash (6f32e22fbf1db308), which I'll file separately.

Anyway, over to nektar@.

Sign in to add a comment