Closed
Bug 1812169
Opened 2 years ago
Closed 2 years ago
[CTW] Bounds incorrect for text within absolute positioned, flex layout, translated container
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1806356
Tracking | Status | |
---|---|---|
firefox111 | --- | affected |
People
(Reporter: nlapre, Unassigned)
References
Details
(Whiteboard: [ctw-m5])
Load the following page with the accessibility cache on:
data:text/html,<div style="position:absolute; display:flex; transform:translate(100%,100%);">test</div>
The bounds of the text leaf accessible in the cache are reported at the top-left of the page, when they should be offset down and to the right by 100%. The bounds are correct with the cache off.
Forcing that div
to create an accessible fixes the problem. This example page has correct bounds, on both the section accessible and its descendant text leaf:
data:text/html,<div tabindex="-1" style="position:absolute; display:flex; transform:translate(100%,100%);">test</div>
This is the very-pared-down version of an issue with LinkedIn, namely the reactions bar popup (such as Like, Love, Celebrate, and so on) that comes up when the mouse enters the Like button area. That popup bar is translated into place, but Firefox is confused on where the bounds of the buttons within it are.
Updated•2 years ago
|
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•