Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors when browsing with Google Chrome with NVDA. This is the latest version of Google Chrome. #5256

Closed
nvaccessAuto opened this issue Aug 1, 2015 · 2 comments

Comments

@nvaccessAuto
Copy link

Reported by Brendon22 on 2015-08-01 03:04
Hello,
When browsing through a website with Google Chrome with NVDA, I get the following error:
Note: this is on most websites not all though.
ERROR - XMLFormatting.XMLTextParser.parse (12:29:12):
XML: <control controlIdentifier_docHandle="18350620" controlIdentifier_ID="-3782" _startOfNode="1" _endOfNode="1" isBlock="0" isHidden="0" _childcount="2" _childcontrolcount="0" _indexInParent="0" parentChildCount="2" IAccessible2::attribute<pseudo="before>" IAccessible2::attribute_display="inline-block" IAccessible2::state_1024="1" IAccessible::role="1060" IAccessible::state_65536="1" keyboardShortcut="" name="Click to share on LinkedIn" >Click to share on LinkedInLinkedIn15
Traceback (most recent call last):
File "XMLFormatting.pyc", line 60, in parse
ExpatError: not well-formed (invalid token): line 1, column 2926
ERROR - XMLFormatting.XMLTextParser.parse (12:29:12):
XML: <control controlIdentifier_docHandle="18350620" controlIdentifier_ID="-3518" _startOfNode="0" _endOfNode="0" isBlock="1" isHidden="0" _childcount="1" _childcontrolcount="1" _indexInParent="1" _parentChildCount="4" IAccessible2::attribute_display="block" IAccessible2::attribute_tag="div" IAccessible2::attribute_xml-roles="main" IAccessible2::state_1024="1"

I am unable to hear the content on the website and I am unable to brows the website correctly:
Website where this happens is the following:
http://www.nvaccess.org/download/
Thank you.

Blocking #5394

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2015-10-08 02:49
This is due to a bug in Chrome. I filed GoogleIssue:chromium:540974.

@jcsteh
Copy link
Contributor

jcsteh commented Mar 30, 2016

Chromium issue 540974 is now fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants