Make automatic say all in virtual buffers optional #414

Closed
nvaccessAuto opened this Issue Jan 1, 2010 · 5 comments

Projects

None yet

2 participants

@nvaccessAuto

Reported by Hermann on 2009-09-14 13:43
When you open a web page, NVDA automatically reads it.
Since modern web pages consist of a lot of repeating stuff - such as
navigation, Google search etc. - one has no need to be read this again and
again, each time you open a page or subpage.
When one needs to have read certain parts of the page, such as newspaper
articles, it is sufficient to use the SayAll function.
So there should be an option to turn automatical reading off, and hear the
page announcements only, e.g. X links Y headings etc. and the percentage of
load while loading.

@nvaccessAuto

Comment 1 by jteh on 2011-02-10 21:31
Link/heading counts, etc. is a separate issue.

Moving this into near-term, since quite a few people have requested it outside of this ticket.
Changes:
Changed title from "The continuous reading of web pages should be made optional." to "Make automatic say all in virtual buffers optional"
Milestone changed from None to near-term

@nvaccessAuto

Comment 2 by jteh on 2011-06-09 03:28
Changes:
Milestone changed from near-term to 2011.3

@nvaccessAuto

Comment 3 by briang1 on 2011-06-09 07:45
The issue then becomes, do you make this function focus on the top of the page or what? If you are coming back to a page where the remembered positon is set, what action do you take and how do you tell its actually loaded?

At the moment, one very seldom hears the 100 percent of a page load, so the say all is the only indication all is well.

@nvaccessAuto

Comment 5 by mdcurran on 2011-09-05 06:55
Implemented in d3008b6.
Changes:
State: closed

@nvaccessAuto

Comment 6 by kevinchao89 on 2011-09-06 12:19
Excellent! This is working very nicely in Snapshot 4634. It certainly is much better than hammering CTRL after a page load. This is very much appreciated!

@nvaccessAuto nvaccessAuto added this to the 2011.3 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment