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
add keystroke to jump to the end of landmarks #5482
Labels
Milestone
Comments
Rather than consuming an extra keystroke, it'd be good if we could have landmarks included in the move past end of container command (comma). This could be a bit tricky, though. |
If I want to give this a try, are there any things I should know? |
derekriemer
pushed a commit
to derekriemer/nvda
that referenced
this issue
Oct 17, 2016
… one using the skip to end/beginning of container command. If there is a container inside of a landmark, this command retains the behavior of only skipping to the end of the container. nvaccess#5482 This needs testing in edge, and look over from someone who knows more about browse mode. Also, I'm not sure why there are two methods, one in virtualBuffers/__init__.py and browseMode.py, so if someone can check my code for sanity, that would be great.
derekriemer
pushed a commit
to derekriemer/nvda
that referenced
this issue
Oct 17, 2016
… one using the skip to end/beginning of container command. If there is a container inside of a landmark, this command retains the behavior of only skipping to the end of the container. nvaccess#5482 This needs testing in edge, and look over from someone who knows more about browse mode. Also, I'm not sure why there are two methods, one in virtualBuffers/__init__.py and browseMode.py, so if someone can check my code for sanity, that would be great.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rationale: Sometimes, mostly in news sites, an aside landamark is found inside a main landmark. That makes the reading experience rather unpleasant. Adding a keyboard command to jump to the end of a landmark would improve the reading experience. Maybe it will make the announcement of the ending would make nVDA too chatty thoguh.
The text was updated successfully, but these errors were encountered: