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

Issue 737718 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

"Renderer unresponsive" dialog comes up when using Jaws screen reader on long webpages

Project Member Reported by nek...@chromium.org, Jun 28 2017

Issue description

Chrome 61 and Jaws 18.
Navigate to a long webpage e.g. the C++ Core Guidelines at:http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines
2. Wait until the page loads and observe that the renderer is responsive.
3. Either:
a) Try to scroll down the page using Jaws Virtual Buffer by repeatedly pressing page down or cursor down.
B) Try focusing the address bar or moving focus repeatedly from the document into the address bar and back by pressing Ctrl+L and F6.
5. Observe that multiple times the "renderer unresponsive" dialog will come up asking you whether you want to "Wait" or "Kill" the renderer.

 
Labels: triage-dougt

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

Labels: -triage-dougt
Labels: a11y-secondary
Project Member

Comment 4 by sheriffbot@chromium.org, Dec 10

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment