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

Issue 691839 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

Empty virtual buffer after interacting with specific pages for a while

Project Member Reported by chaok@google.com, Feb 14 2017

Issue description

Chrome Version: M56Stable and M58 Dev
OS: Win10
Screen Reader: JAWS 18

What steps will reproduce the problem?
(1) Use above combo on: http://www.howtogeek.com/269422/how-to-enable-android-nougats-direct-boot-for-less-annoying-encryption/
(2) Try navigating around the virtual buffer. 

What is the expected result?
Possible to use JAWS commands to interact with page content

What happens instead?
After a few seconds, the buffer becomes empty.

 

Comment 1 by chaok@google.com, Feb 14 2017

Partner uncovered cause of blank virtual buffer:
"document node's MSAA state does not have its readonly MSAA state bit set"
Labels: NewComponent-Accessibility NewComponent-Accessibility-Compatibility
Components: UI>Accessibility>Compatibility
Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 27 2017

Labels: Hotlist-Google
Labels: triage-lpalmaro

Comment 7 by nek...@chromium.org, Aug 31 2017

Status: WontFix (was: Untriaged)
Unable to reproduce in Chrome 62.0.3192.0. It must have been fixed during some related virtual buffer fixes I made previously.

Sign in to add a comment