1790573 - The browser freezes when attempting to read the NVDA Commands Quick Reference with NVDA

Status: RESOLVED WORKSFORME

(Core :: Disability Access APIs, defect)

Description

[Daniel Bodea [:danibodea]]

Attachment: FF freezes when attempting to read NVDA Commands Quick Reference.webm

Note

• When the user sets FF as the default browser, launches NVDA, open's the NVDA settings context menu and launches the NVDA Commands Quick Reference document (a local file), and immediately taps some document reading commands, he may notice a complete freeze of the browser.

** Found in**

• Nightly v106.0a1

Affected versions

• Nightly v106.0a1

Tested platforms

• Affected platforms: Windows 10 (NVDA)
• Unaffected platforms: MacOS, Ubuntu

Steps to reproduce

1. Make FF default
2. Launch NVDA
3. Tap NVDA + SPACE (INS/CAPSLOCK + SPACE)
4. Navigate to Help / Commands Quick Reference
5. Tap "H" key (to read headers)

Expected result

• Headers are read correctly.

Actual result

• The browser freezes completely.
• If NVDA is closed, the browser unfreezes.

Regression range

• Not a recent regression of FF since it was reproduced on ESR 91.

Additional notes

• This issue is somewhat intermittent. If enough time is allowed for the document to be properly read, the freeze might not occur.
• It was reproduced on 2 different machines to make sure it is not caused by local settings.
• NVDA version: 2022.2.2

Comment 1

[James Teh [:Jamie]]

I can't seem to reproduce this no matter what I do/how many times I try it. Is this with installed copies of Firefox (using the installer) or with zip archives? Note that if the installer isn't used, Firefox won't register a component which is needed for proper accessibility performance and functionality (about:support will show Accessible handler used false).

Comment 2

[Daniel Bodea [:danibodea]]

Yes, this is true. A downloaded archived (not installed) build was used when the bug was logged and it does NOT occur on a build that is properly installed. Feel free to change the bug status however fits you. Should I make it a prerequisite to always use installed builds for accessibility testing?

Thank you!

Comment 3

[James Teh [:Jamie]]

(In reply to Bodea Daniel [:danibodea] from comment #2)

Should I make it a prerequisite to always use installed builds for accessibility testing?

For now, yes please. However, note that this will no longer be necessary once our current accessibility engine re-architecture project (Cache the World) ships in a few months.