Open cary-rowen opened 1 day ago
Hi cc @NSoiffer Can you take a look at this?
Many thanks
It worked for me yesterday or the day before that on Chrome. I don't remember what the version was. Version 131.0.6778.71 and the just updated Version 131.0.6778.86 are not triggering the calls to MathCAT. Everything is working in Firefox. Edge Version 131.0.2903.51 has the same problem as Chrome (not surprisingly). The problem is also there in Chrome Canary Version 133.0.6849.0.
I suspect the stable build on Nov 12 (131.0.6778.70) was working. However, Google doesn't make it easy download old versions and I failed in my attempt to download that version.
Note 1: on my Windows 10 computer, there is no speech period, let alone the ability to navigate it.
Note 2: NVDA 2025.1 alpha builds fails for navigation of math with MathCAT due to a problem in NVDA's braille code. That's a separate issue that I hope to file a bug report on in the next few days. It is not a problem for 2024.4 (or 2024.4.1).
If you report this to Chromium as well, please post the link here so we can track it as well.
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