23981 2013-12-03 16:51:13 +0000 AAPI and non-rectangular path 2014-01-20 23:29:15 +0000 1 1 1 Unclassified HTML WG CR HTML Canvas 2D Context unspecified PC Windows NT CLOSED WONTFIX a11y_canvas P2 normal --- 1 plh jaymunro jmann mark.sadecki+w3c mike public-html-admin public-html-wg-issue-tracking schwer public-html-bugzilla oldest_to_newest 97061 0 plh 2013-12-03 16:51:13 +0000 Can existing AAPIs be notified of non-rectangular paths? If AAPIs can only receive rectangular areas, what is the expectation on the user agent? 97087 1 jaymunro 2013-12-03 21:34:55 +0000 Reassigning to Canvas 2D Context Level 2 since drawSystemFocusRing and drawCustomFocusRing are at risk for CR. 97121 2 schwer 2013-12-04 14:53:32 +0000 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. 97139 3 plh 2013-12-04 17:56:36 +0000 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. 97151 4 jaymunro 2013-12-04 19:47:22 +0000 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. 98380 5 plh 2014-01-13 23:48:12 +0000 Works for me. No action needed. 98795 6 jmann 2014-01-20 23:29:15 +0000 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.