-
-
Notifications
You must be signed in to change notification settings - Fork 783
NVDA cannot navigate math content in Chromium #17421
Copy link
Copy link
Closed
Labels
app/chromeblocked/needs-external-fixp2https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Metadata
Metadata
Assignees
Labels
app/chromeblocked/needs-external-fixp2https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Type
Fields
Give feedbackNo fields configured for issues without a type.
This is most likely a Chromium regression, but it's unclear which version introduced it. I hope the community can provide more information. In the meantime, I will report this issue to the Chromium team.
Steps to reproduce:
Actual behavior:
Note: Using object navigation (NVDA+numpad4/6), you can locate the mathematical content, but interaction is still not possible.
Expected behavior:
NVDA should be able to interact with math content in Chromium, just like it does in Firefox.
NVDA logs, crash dumps, and other attachments:
System configuration:
NVDA installed/portable/running from source:
Installed
NVDA version:
2024.4.1 (Alpha snapshot)
Windows version:
Windows 10 22H2 (AMD64) Build 19045.5131
Name and version of other software in use when reproducing the issue:
Chrome 131.0.6778.86
Other information about your system:
None
Other questions:
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please describe their behavior:
The issue can be reproduced in versions 2024.1, 2024.2, and 2024.3.
If NVDA add-ons are disabled, does the problem still occur?
Yes
Does the issue still occur after running the COM Registration Fixing Tool in NVDA's tools menu?
Yes