Re: Unknown Content in Firefox
|
Gene
Very unlikely. this is likely the result of
some dll files that are unregistered. This is a well known problem to list
members who see it discussed frequently. It often results from Microsoft
Word or, I believe other Microsoft office products being uninstalled. The
files need to be registered again in a procedure list members will, assumedly,
provide.
There was nothing in the original message
indicating that any add ons were used. Unless we get more information,
there is no reason to assume add ons have anything to do with the problem,
though asking if add ons are being used is a question that may help solve the
problem. I doubt it but we'll see.
Also, if add ons are the cause of the problem,
experimenting by installing older versions is unnecessary. Firefox can be
run, for test purposes in Safe Mode, in which all add ons are disabled.
This has nothing to do with Windows safe mode. those who know more about
it can tell you how to use it if desired.
Gene ----- Original Message -----
From: Kristin K
Sent: Thursday, January 11, 2018 9:32 AM
Subject: Re: [nvda] Unknown Content in Firefox I use the same configuration – NVDA with Firefox and with the last Firefox upgrade it all blew up…mainly because our Deque add ons didn’t work with the newest version of Firefox. Back it up a couple of versions and you should be okay.
Kristin Knudson | Senior Accessibility Analyst c 410-294-3228
From: nvda@nvda.groups.io
[mailto:nvda@nvda.groups.io] On Behalf Of Tim Harshbarger
Hi,
I have a coworker who needs to be able to use NVDA and Firefox—we use it as part of our accessibility testing. Everyone else seems to be able to use NVDA 2017.3 (or 2017.4) with Firefox 57 with no problems.
However, every time he tries to use NVDA 2017.4 with Firefox 57, NVDA says the content of the page is “unknown”. He says it works ok in Chrome and IE 11. He was also having the problem with NVDA 2017.3.
So far, we have tried de-installing NVDA and re-installing it as well as de-installing Firefox and re-installing it. Neither action fixed the problem.
Has anyone else run into this problem and been able to resolve it? If not, does anyone have any suggestions for what we might try next?
Thanks, Tim
|
|
|