New issue
Advanced search Search tips

Issue 915770 link

Starred by 2 users
Status: Assigned
Owner:
leberly@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

VoiceOver goes into "busy" state after deleting a message in Gmail

Project Member Reported by vtsaran@google.com, Dec 17 
Chrome Version: 71.x
OS: 10.14.2

What steps will reproduce the problem?
(1) Start VoiceOver (CMD+F5 or CMD + power button three times on Touchbar Macbooks)
(2) Open gmail.com, sign in, open one of the email threads
(3) After reading an email message, press "e" to archive it, then observe

What is the expected result?
VoiceOver should announce the next thread in focus

What happens instead?
VoiceOver goes into "busy" state by blocking keyboard input and saying "busy" with every key press



More information:
the work-around seems to be either to restart VoiceOver or to switch to another window and wait a bit

Comment 1 by leberly@chromium.org, Jan 5

Components: -UI>Accessibility UI>Accessibility>Compatibility
Status: WontFix (was: Untriaged)
Chrome 73.0.3643.0 (Official Build) canary (64-bit)
Chrome 71.0.3578.98 (Official Build) (64-bit)
Mac OS 10.13.6 High Sierra 

I am unable to repro on both Chrome canary and stable per the above steps, I do not get any busy messages. I'm also on a high end Mac with 16GB of RAM that was freshly rebooted. 

I'm going to close as WontFix; however, Victor, if you have other ideas about how to repro please reopen and let me know.

Comment 2 by vtsaran@google.com, Jan 5

Status: Untriaged (was: WontFix)
Definitely reopenning as I see this occur many times per day. All I suggest is perhaps to try with larger threads, perhaps with five messages or more.

Comment 3 by vtsaran@google.com, Jan 5 

Safari does not have this issue with the same hardware configuration and the same email thread.

Comment 4 by leberly@chromium.org, Jan 8

Owner: leberly@chromium.org
Status: Assigned (was: Untriaged)
Assigning to myself to investigate further.
►

Sign in to add a comment