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

when pressing NVDA+f5, NVDA should update document and put in the same position #2032

Closed
nvaccessAuto opened this issue Jan 6, 2012 · 5 comments

Comments

@nvaccessAuto
Copy link

Reported by drein on 2012-01-06 18:35
When we are in browse mode, and press nvda+f5, NVDA bring the virtual cursor to the top of document.
When possible, it should be suitable to have the cursor to the same position before pressing NVDA+f5.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2012-01-06 22:27
This is really more of a debugging/emergency command and shouldn't be necessary in normal usage. It'd be better to file bugs concerning the particular cases where this is required. They're probably browser bugs, but we can then attempt to get them fixed in the browsers.

@bhavyashah
Copy link

bhavyashah commented Aug 7, 2017

@jcsteh Your #2032 (comment) is slightly unclear to me. Pressing NVDA+F5 always dislaces the focus to the top of the document rather than there being particular cases where this behaviour is shown. Could you please clarify?

@jcsteh
Copy link
Contributor

jcsteh commented Aug 7, 2017

My point is that this command is more meant for diagnosing problems, rather than something that users should actually use in real world usage. So, having it return focus to the right place isn't something we consider important because it shouldn't be necessary in real world usage anyway. If there are cases where you need to use NVDA+f5, those should be filed specifically and addressed.

@bhavyashah
Copy link

@jcsteh Okay, but if specific cases should be filed separately, can we close this ticket?

@jcsteh
Copy link
Contributor

jcsteh commented Aug 7, 2017

That's a fair point. Closing as won't fix.

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

3 participants