[Tracking Requested - why for this release]: High visibility bug between accessibility support in Firefox and the major commercial assistive technology vendor in one of the most used web applications out there: Gmail.
When using Firefox and JAWS together, performance is very bad in Gmail. Many other pages, even those with big tables such as a Pushlog view on M-C, or a SearchFox results page or file view, are OK when compared to NVDA. But Gmail exhibits the following problems:
- Arrowing through a list of conversations such as Inbox takes 1.5 to 2 seconds before the newly focused item is spoken.
- When composing a message, each focus event such as when tabbing, or when entering recipients, and autocomplete results are being displayed, takes a second or more to react and speak the newly focused item.
Both of these problems go away when turning off JAWS's virtual buffer with JAWSKey+Z.
Something is causing JAWS to constantly rebuild its virtual buffer. Even after we stopped recreating accessible objects unnecessarily, see bug 686400, this is happening.
I've reached out to Vispero, the vendor of JAWS, and the lead developer on their support for Firefox has indicated that he'll look into it from their end, too.
Filing this so it is tracked on our end.