-
-
Notifications
You must be signed in to change notification settings - Fork 655
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
Chromium browsers issue with mouse tracking/reading #17613
Comments
Hi, I don't quite understand your description, it seems a bit vague. Mouse tracking works fine on NVDA alpha 35001 and Chrome version 131.0.6778.265 (official) (64-bit), reporting text, links, etc. in web pages. If you can please clarify the Steps to reproduce and Actual behavior etc. Have you tried the COM Registration Fixing Tool under the Tools menu? Thanks! |
Duplicate of #11845 |
Hi there,
I had given very specific steps to reproduce in chromium-based browsers.
It is as I described.
Any an all elements I try to interact with when using the mouse itself, in all updated versions of browsers, chrome; opera; operaGX, etc., do not register.
I have default settings, no add-ons, and when I try to hover over text or anything else, NVDA does not detect it and says, if anything, “pane unavailable”.
What exactly are you looking for with information?
I am not too technical, so I am unable to give any log errors and such, just the descriptions of things I encounter while trying to use NVDA on windows 11, with any chromium browser, and the mouse tracking/reading function.
I’ve tried the COM Registration Fixing Tool, yes. Sadly, it did not help.
I have tried uninstalling and reinstalling everything related. Ensured multiple times that everything is up-to-date, but nothing is working, and I can only use my keyboard to navigate websites now. No longer can I use my mouse to hover over and read elements.
Is there anything more specific you may be needing? :)
Thank you for your time and response! :)
From: WangFeng Huang ***@***.***>
Sent: Sunday, January 12, 2025 7:55 PM
To: nvaccess/nvda ***@***.***>
Cc: West Palm Beef ***@***.***>; State change ***@***.***>
Subject: Re: [nvaccess/nvda] Chromium browsers issue with mouse tracking/reading (Issue #17613)
Hi,
I don't quite understand your description, it seems a bit vague.
Mouse tracking works fine on NVDA alpha 35001 and Chrome version 131.0.6778.265 (official) (64-bit), reporting text, links, etc. in web pages.
If you can please clarify the Steps to reproduce and Actual behavior etc.
Have you tried the COM Registration Fixing Tool under the Tools menu?
Thanks!
—
Reply to this email directly, view it on GitHub<#17613 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BHCYUJP33MXF2FQXR3UEQN32KM2JFAVCNFSM6AAAAABVBEL66CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBWGEZDQNJTGE>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce:
Either be in Google Chrome, OperaGX, or other chromium based browsers, with or without NVDA started up.
Make sure to have the mouse tracking feature on, so that when a user hovers over text or other elements, it will detect and read them out loud, and/or highlight depending on the visual settings activated.
Actual behavior:
When trying to enter the browser with just the mouse, there will either be a very basic announcement of an element NVDA decides to place the virtual cursor on; no announcement; or it will say, "pane unavailable", and user is unable to have elements read out to them.
Expected behavior:
When user enters browsing window, the mouse can hover over text elements, links, buttons, images, etc., and have them read aloud to the user as they try to read with the mouse.
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
Directly on drive
NVDA version:
Latest as of 1/12/2025
Windows version: 11 - latest as of 1/12/2025
Name and version of other software in use when reproducing the issue:
Windows magnifier for zooming in on text or images.
Google Chrome, OperGX, or other chromium-based browser (as is to my understanding of how these things work, I am definitely not a browser dev...)
Other information about your system:
AMD processor, PNG Nvidia RTX 2070Ti, and 128GB of RAM
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
No.
If NVDA add-ons are disabled, is your problem still occurring?
N/A
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
No
The text was updated successfully, but these errors were encountered: