Problem with standard F5 keystroke is that almost every single browser
will then just reload the page from scratch, losing all DHTML content
changes.


I do also know that NVDA key + number row 5 is meant to turn on
reporting of dynamic content changes, but, it won't always work, partly
since, at times, the webpages document-object-model will be rather
extensive.


Either way, I had just thought/assumed that it was offering/implementing
a form of virtual page buffer refresh, but anyway - will play around
with other keystrokes, alt+tabbing away from window, and back to it,
etc. etc.


Stay well


Jacob Kruger
Blind Biker
Skype: BlindZA
"Resistance is futile...but, acceptance is versatile..."

On 8/14/2018 1:59 PM, Gene wrote:

I believe it does reload the document, because, as I recall, I think
it takes too long than to just refresh the buffer. If so, it is doing
the same thing as just f5. Of course, if you reload the document, you
are reloading the buffer. But try turning browse mode off and then on
with NVDA key space. This may just refresh the buffer.
If NVDA key f5 is explained in the manual, I don't know where. It
isn't discussed in the browse mode section. It is probably mentioned
in the quick reference guide, but it may well not clarify what it does.
Gene
----- Original Message -----
*From:* Jacob Kruger <mailto:jacob@blindza.co.za>
*Sent:* Tuesday, August 14, 2018 5:45 AM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* [nvda] NVDA + F5 hotkey doing an actual document reload

This is something I think has been going on across a few versions of
NVDA now, and, just wanted to confirm that it's not me that's confused.


I am currently making use of Version: alpha-15854,a8bda064, FWIW.


Anyway, I was under the impression that, for example, in a web browser,
the hotkey combination of NVDA + F5 should repopulate the virtual buffer
rendition of the page contents - I do need this at times since I work
with dynamic web contents - but, it seems to, literally, just reload the
page as if you'd clicked on something like the browsers own refresh
button, or as if you'd in fact told NVDA that the next keypress should
be passed directly through to the operating system?


Or am I incorrect in having thought it only repopulated a form of
virtual buffer for the webpage?


TIA


Jacob Kruger
082 413 4791
Skype: BlindZA
"Resistance is futile...but, acceptance is versatile..."