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

Jump to bottom

When pressing up or down on the arrow keys to read a web page nvda will freeze. #2409

Closed
nvaccessAuto opened this issue Jun 3, 2012 · 4 comments
Closed

When pressing up or down on the arrow keys to read a web page nvda will freeze. #2409

nvaccessAuto opened this issue Jun 3, 2012 · 4 comments
Labels
bug close/invalid feature/browse-mode

Comments

@nvaccessAuto
Copy link

Reported by meerkat on 2012-06-03 20:20
When I try to press the up or down arrow keys to read a web page, nvda will freeze for a few seconds before continuing to speak.
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2012-06-03 23:08
Please be more specific.

  • Does this happen always or only sometimes?
  • If sometimes, please provide steps to reproduce, web site addresses, etc.
  • Has this only happened since a particular version of NVDA or in all versions?
  • What browser are you using?
  • What version of Windows are you using?
  • Does this happen with the in-built eSpeak speech synthesiser or are you using another synthesiser? If another, please try with eSpeak.

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2012-06-03 23:09
I see you're using Windows 7, so please disregard the operating system question.

@nvaccessAuto
Copy link
Author

Comment 3 by briang1 on 2012-06-04 07:40
There are of course some pages which do run unbelievably slowly when you use nvda to view them, mainly because they take so much processing power to display. This one for example.

http://www.surreycomet.co.uk/
However in XP at least, I've not noticed any increase in this lag over previous versions myself. This applies to bothe main browsers.

@dkager
Copy link
Collaborator

dkager commented Jul 14, 2017

There is quite a lack of information for this issue. Marking it as invalid.

@dkager dkager closed this as completed Jul 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug close/invalid feature/browse-mode
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dkager @nvaccessAuto