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: Bullet And Number Bug #3591

Open
nvaccessAuto opened this issue Oct 20, 2013 · 5 comments
Open

Mouse Tracking: Bullet And Number Bug #3591

nvaccessAuto opened this issue Oct 20, 2013 · 5 comments
Labels
bug feature/mouse-tracking p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority

Comments

@nvaccessAuto
Copy link

Reported by kumajuannazhi on 2013-10-20 19:57
On some webpages, there are times, visually, where a block of static text starts with a bullet or a number. In these cases, if said block is long enough to have been wrapped down one or more lines, NVDA only reads its first line, which is the one with the bullet or number in it, if you're using Mouse Tracking.

@LeonarddeR
Copy link
Collaborator

CC @feerrenrut @Qchristensen

@Qchristensen
Copy link
Member

I just commented on issue #3590 with some more information on mouse tracking in general on the web.

I just expanded the test page I threw together for that issue to put a couple of bullet list items and a couple of numbered list items at the bottom: http://22point.com.au/random/test.html

What I found was:

Edge and IE ignore the text unit resolution and behave as if the resolution is "paragraph". They read the whole bullet point regardless of how long it is.

Firefox works as expected when text unit resolution is set to character, word or line. When set to Paragraph however, it behaves exactly the same as for line - that is, it reads the current line of text of the bullet point.

That issue with Firefox was basically the same thing as I found for reading regular text.

In Chrome, I just can't get mouse tracking to be have at all currently.

Using latest versions of browsers and NVDA 2017.2

@jcsteh jcsteh marked this as a duplicate of #2245 Jul 17, 2017
@feerrenrut feerrenrut added the p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority label Sep 12, 2017
@Adriani90
Copy link
Collaborator

@Qchristensen could you test please with last Alpha? Is this still an issue?

@Qchristensen
Copy link
Member

Using the latest alpha 16440,2d8f08a1 - as well as with 2018.4rc1, I found the same thing as I did in 2017 #3591 (comment)

(Tested in Chrome, Firefox and Edge).

@Adriani90
Copy link
Collaborator

@Qchristensen I am using NVDA 2024.1 Beta 9 and also last alpha version, Firefox 123 and Chrome Canary 124. I cannot reproduce this issue.
The only thing I can reproduce is when there is a link with plain text after the link on the same line or in the same paragraph, NvDA reads out only the link but not the plain text afterwards although it is in the same paragraph.
Can you confirm?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug feature/mouse-tracking p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Projects
None yet
Development

No branches or pull requests

6 participants