This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22803 - Browser manufacturers request clarifying text for drawSystemFocusRing functions
Summary: Browser manufacturers request clarifying text for drawSystemFocusRing functions
Status: CLOSED INVALID
Alias: None
Product: HTML WG
Classification: Unclassified
Component: CR HTML Canvas 2D Context (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11ytf, a11y_canvas
Depends on:
Blocks:
 
Reported: 2013-07-25 17:29 UTC by Rich Schwerdtfeger
Modified: 2016-03-03 15:25 UTC (History)
7 users (show)

See Also:


Attachments

Description Rich Schwerdtfeger 2013-07-25 17:29:01 UTC
During implementation, Google pointed out that it was not clear how styling could be determined that would allow user agents to determine the style applied to the system focus ring and asked that a clarifying note be included. This is text has been shared with the major browser manufacturers and my colleague at Google approved the text and this is being shared with the other browser manufacturers. 

The following change needs to be made to the Canvas 2D API for clarification. It is a Note and does not impact CR. It should either come at the end of step 2 in the drawSystemFocusRing(element) processing or as a note following the definition of drawSystemFocusRing(element) and drawSystemFocusRing(path, element):

Note: User agents may use the <a href="http://www.w3.org/TR/CSS2/ui.html#dynamic-outlines">CSS outlines around focused elements</a> in determining the system focus style on fallback elements to determine the standard system focus ring style drawn on the canvas. This would mean that if an author were to override this style that the appearance of the standard focus ring drawn on the canvas could reflect this change in style.
Comment 1 Jay Munro 2013-07-25 18:00:32 UTC
Would this replace the existing note under step 2? 

"Note: Some platforms only draw focus rings around elements that have been focused from the keyboard, and not those focused from the mouse. Other platforms simply don't draw focus rings around some elements at all unless relevant accessibility features are enabled. This API is intended to follow these conventions. User agents that implement distinctions based on the manner in which the element was focused are encouraged to classify focus driven by the focus() method based on the kind of user interaction event from which the call was triggered (if any)."

or be added to it?
Comment 2 Ian 'Hixie' Hickson 2013-09-12 00:49:36 UTC
I don't really understand how this would work. What if a platform doesn't use 'outline' for focus rings? What if the author is using borders in CSS for focus, instead of outlines? Does it mean that if someone overrides 'outline' on all elements, e.g.:

   * { outline: none; }

...then no outlines will be drawn in <canvas>?
Comment 3 rcabanie 2013-12-01 22:15:26 UTC
Removing CR status as this feature is on the at-risk list and will be removed from the first level
Comment 4 Philippe Le Hegaret 2015-06-16 20:28:22 UTC
Moved back to L1
Comment 5 Philippe Le Hegaret 2015-06-16 20:29:14 UTC
Moved to L1
Comment 6 Philippe Le Hegaret 2015-06-16 20:45:36 UTC
drawSystemFocusRing is no longer. Closing.
Comment 7 Charles McCathieNevile 2016-03-03 15:25:58 UTC
No longer relevant per previous comment