Re: Firefox is driving me crazy!
I don't recall your original message. It is not included in the quoted material in this thread. I don't use a Braille display and I don't know to what extent they are used with screen-readers or independently. If I missed information you wrote, I'm sorry. but since you have older versions of NVDA, the first thing I would do, if you can use speech is to try using NVDA with speech with the Braille display completely off or disconnected. Unless you have done this, it appears to me that the Braille display hasn't been ruled out as the possible problem. I'm not saying it is or isn't. I'm saying that unless you have done something like this, we may not know.
Gene----- Original Message -----
----- Original Message -----
Gosh! I wrote very clearly that I usethe latest Next with Firefox 45.0,
with BOTH a braille display and speech.
I have NO OTHER screen reader, except for older versions of NVDA, which
produce EXACTLY the same result.
ON ALL WEB PAGES.
Il 09/03/2016 19:14, Gene ha scritto:
> The problem appears to be some sort of mismatch between, evidently,
> the browse cursor and the link being clicked on. We don't know what
> is being used as the Braille display. We don't know if the person has
> or can test this with speech. We don't know if the person has or can
> test this problem with another screen-reader. There are many basic
> facts we need to know before proposing that time and effort be spent
> in trying various possible solutions.
> ----- Original Message -----
> *From:* Brian Vogel <mailto:britechguy@...>
> *Sent:* Wednesday, March 09, 2016 10:14 AM
> *To:* email@example.com <mailto:firstname.lastname@example.org>
> *Subject:* [nvda] Re: Firefox is driving me crazy!
> This is a pure SWAG on my part, but I've encountered so
> many bizarre problems caused by cache corruption that the first thing
> I'd recommend is that you clear all browser cache in Firefox. If you
> use CCleaner it will work (and a bit faster) or you can follow the
> instructions on the Firefox Clear Cache
> Try that and see if it resolves the problem. If it doesn't
> at least we can eliminate cache corruption as the root cause.