Re: NVDA 2018.3.1rc1 fix for Firefox crashing
There were certain kinds of refreshes that JAWS couldn't stop. I don't know if that is still true because I very seldom use JAWS now. But Firefox gave the user the ability to have the browser notify the user when the page wanted to redirect or refresh and, as far as I know, that blocked all such efforts.
Why was the feature removed? Was there even proper consultation between the developers and those who work on accessibility? Didn't any blind beta testers notice and complain about the removal? Who knows. I see no reason that it needed to be removed. I see no way in which new features added in the Quantum version make it necessary to remove the feature. But whether I am right or wrong, this topic needs to be addressed by the developers, either by publicly explaining the necessity of the feature's removal or by implementing it again.
----- Original Message -----
From: Ron Canazzi
Sent: Wednesday, September 19, 2018 2:09 PM
Subject: Re: [nvda] NVDA 2018.3.1rc1 fix for Firefox crashing
Going back to about 7 or 8 years ago, I find that even with JAWS feature of repressing page refreshes, for some reason, web pages still continued to refresh over and over again. I am wondering if for some reason, this feature--whether it is screen reader based or browser based simply doesn't work any more. I remember reporting on the beta team years ago about Yahoo Sports--which refreshed every 30 seconds or so during ongoing sports games and neither the Firefox nor the JAWS page refreshed did anything to stop the refreshes. This is perhaps a web design issue as much as anything else and may be why Mozilla eliminated this feature.
On 9/19/2018 2:46 PM, Gene wrote:
-- They Ask Me If I'm Happy; I say Yes. They ask: "How Happy are You?" I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"