This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Can existing AAPIs be notified of non-rectangular paths? If AAPIs can only receive rectangular areas, what is the expectation on the user agent?
Reassigning to Canvas 2D Context Level 2 since drawSystemFocusRing and drawCustomFocusRing are at risk for CR.
No. What is more, Cynthia Shelly, insisted that the focus ring be converted to a rectangle to be consistent with the Windows platform. None of the accessibility APIs on any platforms take a non-rectangular path. Also, when you get to the layout engine in Mozilla we are looking at rectangles and not paths for hit testing. Having a non retangular path would require a rewrite of accessibility APIs across all platforms - desktop and mobile.
Rereading the specification, I see "The methods above are intended to enable this by allowing the user agent to report the bounding box of the path used to render the focus ring as the bounds of the element element passed as an argument, if that element is focused, and the bounding box of the area to which the user agent is scrolling as the bounding box of the current selection." This bug can be closed as far as I am concerned.
I jumped the gun on moving to L2, there are still ongoing discussions on the focus ring methods. Moving back to CR until discussions are complete.
Works for me. No action needed.
As per our Canvas SubGroup discussion, http://www.w3.org/2014/01/13-html-a11y-minutes.html, Philippe has agreed to won't fixing this bug. All accessibility APIs provide location using a bounding rectangle.