Open nvaccessAuto opened 10 years ago
CC @FeerRenrut @QChristensen
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
@Qchristensen could you test please with last Alpha? Is this still an issue?
Using the latest alpha 16440,2d8f08a1 - as well as with 2018.4rc1, I found the same thing as I did in 2017 https://github.com/nvaccess/nvda/issues/3591#issuecomment-315263276
(Tested in Chrome, Firefox and Edge).
@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?
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.