um, I just updated to version 89.0 and I've not seen any issue what so ever.
toggle quoted messageShow quoted text
On 3/06/2021 2:44 pm, Jackie rambled on about the following:
press ctrl l & run about:config. Press the button to tell them you'll
accept the risk. Search for the word accessibility. Having thus said,
that does not appear to be the problem.
Jamie can't reproduce this on any system in his possession, but he & I
will be working together tomorrow evening my time, Friday morning his,
to see if we can't reach some sort of conclusions.
On 6/2/21, Ron Canazzi <aa2vm@...> wrote:
I m wondering that if by default Firefox 89 is having the box concerning
blocking accessibility checked checked by default. If this is true,
there is a way using a hack of some sort involving the configuration
editor to uncheck it without having to use sighted assistance.
Unfortunately, I seem to have deleted the information concerning just
how this is done.
On 6/2/2021 2:16 PM, Jackie wrote:
Obviously not, since I'm the 1 who actually started this thread. Given--
that at least 1 other individual is experiencing this, & given that
Mozilla has made significant underlying changes to its interface, I'd
seriously suggest updating w/caution. I guess I'll not comment any
more though, because Narrator & Jaws don't work w/it either, so I
think this is not an issue w/NVDA, & I apologize for posting regarding
Interestingly, if I start firefox when choosing a profile every time,
it works. If I select any profile & start it up w/o asking, it blows
up. In other words, even if I choose a profile from the profile list
and start it, everything's fine. If I load the same profile
automatically, stuff craters. Go figure! How the firetruck does one
report that & be believable?
On 6/2/21, brice Mijares <bmijares33@...> wrote:
Are you the only one having this problem? I'd like to know, that a way I
can say no to the update. thanks.
On 6/2/2021 9:49 AM, Sue J. Ward wrote:
Hello. I am experiencing the same thing with NVDA, I uninstalled and
reinstalled firefox, ran the calm registration tool, created a new
profile, still nothing and did a system file check, did not find
anything. According to the scan everything was fixed on my windows10
home machine. That is the one I am on right now writing out the email.
Whenever I go to the website just to give you an example cbsnews.com,
I load it on to firefox and getting unknown message whenever I tab
around the page think it loads, whenever I press the arrow keys it
says unknown, am tabbing around again it comes up with unknown but am
not sure what is going on, but when I am going in to the help section,
I have to run the trouble shoot mode, it restarts in trouble shoot
mode everything is fine when am on a website so what is going on here?
I am not on a network of any kind just your typical modem from Cox.com
using a wired connection. However I do have a second machine windows10
pro 64 bit and both the home machine and the pro machine have
everything up to date and are running 64 bit, it is weird on the
windows10 pro I did not have to do anything firefox works great on
that one verses the home machine. I can not figure out why I have to
restart firefox in trouble shoot mode on the windows home machine. I
even did a reset think that would help, no such luck there. In fact I
did load jaws, nothing there. Could someone tell us what is going on
here? Thank you.
Amazon Has Plans to Share Your Internet on June 8
Trump's Blog Page Is No More
Florida Man Cites 'Stand Your Ground' in Iguana Killing
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!"