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
Reading entire documents #5535
Comments
What browser are you using? Also, in the GitHub comment example, what
unit did you have your mouse resolution set to (line, word, etc.)?
|
I am using the latest version of Mozilla Firefox. It is set to Paragraph. However, no matter what I change it to, it still has the same effect. |
OK, so the mouse setting Text unit resolution does change something. It changes the effect of moving your cursor along published text, such as my comment above, what it doesn't change is text that is being typed in a text box. It does not change this for edited text in browse mode either. |
Reading the entire comment is expected behaviour if set to paragraph. It's certainly not expected behaviour if set to line or word. Regression introduced by #1668. |
Yes, agreed. |
…s the appropriate line, word, etc. as expected instead of the entire content. Fixes #5535.
Incubated in d8d5dcf. |
This is now fixed. |
Hello,
When reading a large document with the mouse, such as a php file or css file, where ever you put the mouse NVDA reads from the beginning. In the last update 2015.3, NVDA read from wherever you put your mouse.
The setting under Mouse Options Text Unit Resolution no matter what set to, the same behavior still happens.
The same behavior also occurs in the GitHub comment text field. If I put my mouse at the center of my comment, it starts from Hello, and reads on.
Thanks.
The text was updated successfully, but these errors were encountered: