This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This happens when drawCustomFocusRing returns true (ie the focus ring wasn't drawn by the user agent because the user didn't request a particular focus ring). In this case, the web app would need to draw the focus ring itself. How does the web app inform the user through the AAPI? [[ scrollPathIntoView can't be used to notify accessibility software of the focused object location as-is because it doesn't have an element to fire on, and it doesn't know if the scrolling is because of focus or not. ]] http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Oct/0002.html
Reassigning to Canvas 2D Context Level 2 since drawSystemFocusRing and drawCustomFocusRing are at risk for CR.
Moved to L1
drawCustomFocusRing is no longer. closing.