Consider temporarily freezing dynamic pages with virtual buffers

nvaccess / nvda

NVDA, the free and open source Screen Reader for Microsoft Windows

https://www.nvaccess.org/

Other

2.1k stars 634 forks source link

Consider temporarily freezing dynamic pages with virtual buffers #8079

Open feerrenrut opened 6 years ago

feerrenrut commented 6 years ago

Discussion

See the following issues.

Dynamic finance site is laggy and difficult to use in Chrome. #8078
Say all (nvda+a) repeats certain content on specific websites in firefox #8010

Some sites that have refreshing/dynamic content are quite hard to read, and can cause problems for say all. Consider temporarily freezing these pages.

LeonarddeR commented 6 years ago

To make sure, are you suggesting freezing these pages during say all?

Brian1Gaff commented 6 years ago

A toggle? I know that obviously this can mean some stuff clicked might not work, but most of these pages tend to be scrolling things or opening windows dynamimacally and hence the content goes away when you try to find it otherwise. Brian

zahra21 commented 6 years ago

hi. i confirm this issue unfortunately in any version of firefox which i tested! for example: in www.quora.com i cant signIn without enabling javascript recently. when i activate javascript, the page becomes dynamic and refreshing. simply it causes my keyboard not work, cant navigate web page, or even nvda reads after 20 or 30 seconds! after two or three hours and characters of this site increases to for example: 89000 characters, my firefox becomes unresponsive and nvda becomes silent!

Adriani90 commented 6 years ago

Is this issue still in pipeline for being considered in near NVDA versions?

lukaszgo1 commented 5 years ago

Any updates on this? Any chance of fixing it for 2019.1? It is even more annoying than clickable several time in a row was in my subjective opinion.

Adriani90 commented 5 years ago

@leonardder

Von meinem iPhone gesendet

Am 05.12.2018 um 21:21 schrieb Łukasz Golonka notifications@github.com:

Any updates on this? Any chance of fixing it for 2019.1? It is even more annoying than clickable several time in a row was in my subjective opinion.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

lukaszgo1 commented 4 years ago

Could someone more experienced estimate how hard it would be to fix this one?

Adriani90 commented 4 years ago

Note also the tab freezing feature which has been introduced since Chrome 79: https://www.tenforums.com/tutorials/146276-how-enable-disable-tab-freezing-google-chrome.html

Adriani90 commented 4 years ago

Nevertheless, this has been fixed now with #11190. I am closing as works for me but feel free to comment if I am wrong and we can reopen it.

XLTechie commented 4 years ago

@Adriani90, while tab freezing may address the comment by @zahra21, it doesn't touch the initial issue at all.

Tab freezing can not be activated manually, only as an automatic process after five minutes in the background. In order to help with the issue as described, it would need to be activated manually, or somehow by say all.

feerrenrut commented 4 years ago

The linked chrome feature is about avoiding performance costs for tabs you are not currently using. This issue is about creating a static "view" of the page you are currently reading, with the goal of improving the user experience on dynamic sites that are hard to read / navigate with a screen reader.

The goal would be to allow the user to manually trigger a virtual buffer freeze, read the content they are interested in, then unfreeze the virtual buffer (triggering a refresh of the information stored in the virtual buffer)