Closed Bug 1665632 Opened 5 years ago Closed 7 months ago

Incorrect bounding box locations reported for rotated elements

Categories

(Core :: Disability Access APIs, defect, P3)

Product:
Core
Component:
Disability Access APIs
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

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.)

  1. Turn on Windows Speech Recognition on Windows 10 2004 (set to English).
  2. Navigate to https://hsivonen.fi/fission-host.html
  3. Say "Click button"
  4. Say "three"
  5. 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.

Severity: -- → S3
Priority: -- → P3

Possibly related: bug 1472125, bug 1613626, bug 1649239.

Blocks: boundsa11y
See Also: → 1732179

This was likely fixed as part of the Cache the World project.

Nathan, are you in a position to be able to verify that this is fixed without too much work?

Flags: needinfo?(nlapre)

Just tested. Turns out Windows 11 still has support for WSR, though they mention all over that it'll be removed soon in favor of Voice Access. Anyhow, this works for me now. The bounds of the button drawn by WSR show up as an upright (non-rotated) rectangle, as I'd expect. It's in the right place, and saying "three, OK" successfully clicks the button. In light of this, closing this bug as fixed.

Status: NEW → RESOLVED
Closed: 7 months ago
Flags: needinfo?(nlapre)
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.