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

Mouse Tracking Glitches #3589

Closed
nvaccessAuto opened this issue Oct 20, 2013 · 6 comments
Closed

Mouse Tracking Glitches #3589

nvaccessAuto opened this issue Oct 20, 2013 · 6 comments

Comments

@nvaccessAuto
Copy link

Reported by kumajuannazhi on 2013-10-20 19:15
When you are using the mouse in any web browser with Mouse Tracking enabled, there are times when, visually, a hyperlink is placed within a line, and then there is text after it on the same line. When using the mouse, NVDA will read the text before the link, but then it'll stop. It won't read the link itself either. Also, if a link is at the very start of a line, NVDA will read that link, but it won't read the text that follows. Plus, things get really glitchy when there are multiple links and occurrences of static text within the same line.

@LeonarddeR
Copy link
Collaborator

@Qchristensen, here is another mouse tracking bug. May be we should close some of these and use one issue for all these mouse tracking issues.

@Qchristensen
Copy link
Member

This is similar to #3590 and others, and likely they are related. There is a good chance that fixing one issue in this area will fix others.

@bhavyashah
Copy link

In case @Qchristensen's hunch is correct and fixing one of these mouse tracking issues will effectively resolve others, one of these tickets should probably be assigned a high priority. Thoughts? @feerrenrut

@Qchristensen
Copy link
Member

Thanks Bhavya, definitely do take my comments with the knowledge that I haven't looked at the code and was just going on the basis that there are several issues which all basically fit under the broad problem of "where reading starts and stops when moving the mouse over text".

@Brian1Gaff
Copy link

Brian1Gaff commented Sep 8, 2017 via email

@feerrenrut
Copy link
Contributor

Without more specifics about the problem its hard to tell how this is different from #3590 where @Qchristensen has done a fantastic job of outlining the behaviour in a bunch of different cases. I will close this issue as a duplicate of #3590

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

6 participants