Re: Firefox 57 etc


Brian's Mail list account
 

Indeed, However I am critical of Mozillas handling of this. Its not often that the makers of Jaws put up a page about the pitfalls and also criticise a particular company for being unthinking about their policy toward the VI community.

Let us hope that somebody in the management at that organisation takes us more seriously, however I'm not holding my breath, and I'm not sure if jamie working for them will help much if the culture is going down the road toward making all software inaccessible to stop hacking. He is probably not the most tactful person in the world as indeed neither am I. I can now afford to grow old disgracefully. Age has its advantages as history does tend to repeat itself and we have all been here before, sadly.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "никита тарасов" <ntarasov29@...>
To: <nvda@nvda.groups.io>
Sent: Friday, November 03, 2017 6:41 PM
Subject: Re: [nvda] Firefox 57 etc



Hello. I don't think it's worth installing Mozila 57 until she's fully available to NVDA.
Отправлено из Почты для Windows 10

От: Brian's Mail list account via Groups.Io
Отправлено: 3 ноября 2017 г. в 21:17
Кому: nvda@nvda.groups.io
Тема: Re: [nvda] Firefox 57 etc

Yes I saw a message on the issues list from James, about some fixing for
version 58, so maybe it will get resolved from the currently unusable state.
Its new users of any screenreader I feel sorry for, especially where its a
shared machine and the sighted member just lets firefox update.
There are a couple of other issues. It disabled both my add ons,
navigational sounds and Ublock Origin ad blocker and even when I put the
version 52 back on I had to re download both add ons and install them again.
Not only that but nvda after the update could not read the screen of the add
ons manager, I had to exit firefox completely and go back in again to see
if they had installed correctly, I'm sure this was not the case prior to up
and down dating the version I had, which was 55. How also does one set 52 to
get security updates without letting it update to 57 as I see it wants to do
till I set updates to no, ie not recommended.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Robert Mendoza" <lowvisiontek@...>
To: <nvda@nvda.groups.io>
Sent: Friday, November 03, 2017 10:31 AM
Subject: Re: [nvda] Firefox 57 etc


Hi, Brian


I have the same issue on the other machine, and that is the reason why I
keep to shift instead to use the Firefox ESR version 52 but for now I will
stick to this version because there is likely more stable in performance
and never has a problem. And, once the issue has fix maybe I could go for
to use and test it again.


Robert Mendoza

On 11/3/2017 6:00 PM, Brian's Mail list account via Groups.Io wrote:
With regard to this version of Firefox, and in addition to what Joseph
posted about it. Here is what me acting as the average unaware updater
found.
After installation only the menus work, no content on the page is
readable, you cannot go into any browse or focus mode. You just here
unknown.
Now there may well be some kind of setting that can be altered, I do not
know, to achieve what he got, slow but functioning. I could not find any
option for this. Not only that but it seemed to lose almost half of my
bookmarks as well.

So unless they fix this on the release version anyone trying to use
Firefox 57 when it comes out with the latest version of nvda, and I am up
to date with the master branch here, will not be able to do so unless
they know how to make it work.
If these people are employees then they will probably need the permission
of an admin to reinstall a version like 55, and turn off auto updates. I
have reinstalled 52 in actual fact and got my bookmarks back as well as
functionality. To my mind the makers of Firefox at the current state of
play should be able to see if screenreading software is on a machine in a
similar way to Adobe reader or Jarte does, and prevent it from updating
to an unworkable version.
I cannot understand why they have not done this.

Anyone care to comment?
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.



Join nvda@nvda.groups.io to automatically receive all group messages.