Open
Bug 1665632
Opened 4 years ago
Updated 3 years ago
Incorrect bounding box locations reported for rotated elements
Categories
(Core :: Disability Access APIs, defect, P3)
Core
Disability Access APIs
Tracking
()
NEW
People
(Reporter: hsivonen, Unassigned)
References
(Blocks 1 open bug)
Details
Steps to reproduce
(The test case is a Fission-motivated test case, but this is a non-Fission bug.)
- Turn on Windows Speech Recognition on Windows 10 2004 (set to English).
- Navigate to https://hsivonen.fi/fission-host.html
- Say "Click button"
- Say "three"
- Say "OK"
Actual results
The between steps 3 and 4, the overlay labeled "3" does not appear over the rotated button labeled "Button". After step 5, the click goes to where the overlay was and not to the button.
Expected results
Expected the overlay for the third button to be the upright bounding box for the rotated button.
Additional info
We do place IME pop-ups correctly, so the code path for reporting those coordinates to the system works.
Updated•4 years ago
|
Severity: -- → S3
Priority: -- → P3
Comment 1•4 years ago
|
||
Possibly related: bug 1472125, bug 1613626, bug 1649239.
Updated•4 years ago
|
Blocks: boundsa11y
You need to log in
before you can comment on or make changes to this bug.
Description
•