Open
Bug 1836944
Opened 2 years ago
Updated 2 years ago
Wrong MSAA positions on dynamic elements since introduction of accessibility cache
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: reinhold.fruesmer, Unassigned)
References
(Blocks 1 open bug)
Details
Steps to reproduce:
- Ensure 'accessibility.cache.enabled' is set to true (default)
- Browse to https://samples.gwtproject.org/samples/Showcase/Showcase.html
- Expand section 'Lists and Menus' in the sidebar on the left side.
- Check position of the 'List Box' element using an accessibility tool like inspect.exe by Microsoft
Actual results:
The position given by Firefox accessibility interface is definitely wrong, which can be proved e. g. by capturing a screenshot and checking the position inside an imaging application.
Expected results:
Setting 'accessibility.cache.enabled' to false gives correct position again, but is undesired - should work correctly without having to disable the cache (if possible).
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Disability Access APIs' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Component: Untriaged → Disability Access APIs
Product: Firefox → Core
Updated•2 years ago
|
Blocks: boundsa11y, a11y-ctw
Severity: -- → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•