Note: There are a few cases of duplicates in user autocompletion which are being worked on.

JAWS virtual buffer becomes inaccessible frequently w/ JS enabled or disabled

RESOLVED FIXED in mozilla23



Disability Access APIs
4 years ago
4 years ago


(Reporter: Everett Zufelt, Unassigned)


20 Branch
Windows 7

Firefox Tracking Flags

(Not tracked)




4 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:21.0) Gecko/20100101 Firefox/21.0
Build ID: 20130423212553

Steps to reproduce:

1. Firefox was automatically updated to 20.1 (also tried on 21 beta)
2. Tried to access sites I use commonly (, both were accessed as an authenticated user. This happens on some other sites as well.
3. After viewing a few pages on the site JAWS would no longer read from virtual buffer.
4. Disabling virtual buffer I could tab through the site and JAWS would read focused item.
5. Turning virtual buffor back on JAWS would not read anything.
6. Refreshing virtual buffer did not help.
7. Starting Firefox with extensions disable did not help
8. Resetting Firefox did not help.
9. Trying with JS disabled seemed to lengthen duration on sites before problem appeared.

Actual results:

JAWS will not read virtual buffer.

Expected results:

JAWS should be able to read virtual buffer.

Comment 1

4 years ago
Using JAWS 13 or JAWS 14 on Windows 7 Professional. Problem only began to manifest after Firefox 20.1 update.

Comment 2

4 years ago
Tentatively, this is a dupe of bug 865240. Alex, do you agree?
Component: Untriaged → Disability Access APIs
Product: Firefox → Core
Version: 21 Branch → 20 Branch

Comment 3

4 years ago
(In reply to Marco Zehe (:MarcoZ) from comment #2)
> Tentatively, this is a dupe of bug 865240. Alex, do you agree?

very similar
Depends on: 865240

Comment 4

4 years ago
fixed by bug 865240 (per bug 865240 comment #21)
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
You need to log in before you can comment on or make changes to this bug.