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 23979 - The differences between drawSystemFocusRing and drawCustomFocusRing should be better highlighted in the specification
Summary: The differences between drawSystemFocusRing and drawCustomFocusRing should be...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: CR HTML Canvas 2D Context (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 major
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11y_canvas
Depends on:
Blocks:
 
Reported: 2013-12-03 16:48 UTC by Philippe Le Hegaret
Modified: 2015-06-16 20:38 UTC (History)
5 users (show)

See Also:

Attachments

Description Philippe Le Hegaret 2013-12-03 16:48:09 UTC 
The differences between drawSystemFocusRing and drawCustomFocusRing should be better highlighted in the specification:

 * Using drawCustomFocusRing means that the web app intention is to draw the focus itself, unless the user has requested a particular focus ring. Its purpose is to help the web app preserves the user setting

 * Using drawSystemFocusRing means that the web app wishes to delegate the drawing of focus ring to the user agent
Comment 1 Jay Munro 2013-12-03 21:28:46 UTC 
reassigning to Canvas 2D Context Level 2 since drawSystemFocusRing and drawCustomFocusRing are at risk for CR.
Comment 2 Rich Schwerdtfeger 2013-12-04 14:36:28 UTC 
I think the general agreement between browser manufacturers would be to push drawCustomFocusRing to L2 eliminating this issue for V1. Part of my reason for doing this would be to give more time for media queries to show up and use them to determine if the author is in working with a high contrast system setting turned on. This also eliminates the confusion stated here.

This would allow us to focus only on drawSystemFocusRing. We cannot afford to have low vision users wait for L2.
Comment 3 Jay Munro 2013-12-04 19:46:21 UTC 
I jumped the gun on moving to L2, there are still ongoing discussions on the focus ring methods. Moving back to CR.
Comment 4 Michael[tm] Smith 2013-12-06 06:58:36 UTC 
(In reply to Rich Schwerdtfeger from comment #2)
> I think the general agreement between browser manufacturers would be to push
> drawCustomFocusRing to L2 eliminating this issue for V1.

Having also followed the implementer discussions, I concur with Rich here that there's general agreement among the browser implementers to not go ahead in implementations with drawCustomFocusRing as it's currently specified. In fact as far as the spec goes,  I think it's pretty clear that there are no implementers who'd object to the group deferring drawCustomFocusRing.

> Part of my reason
> for doing this would be to give more time for media queries to show up and
> use them to determine if the author is in working with a high contrast
> system setting turned on. This also eliminates the confusion stated here.
> 
> This would allow us to focus only on drawSystemFocusRing.

Yeah, it seems clear we're a lot closer to general agreement for drawSystemFocusRing, so decoupling drawSystemFocusRing from discussion of drawCustomFocusRing would help un-muddy the waters.
Comment 5 Rich Schwerdtfeger 2013-12-16 23:52:23 UTC 
move to L2
Comment 6 Philippe Le Hegaret 2015-06-16 20:27:24 UTC 
Moved back to L1
Comment 7 Philippe Le Hegaret 2015-06-16 20:36:34 UTC 
we now only have drawFocusIfNeeded, so this bug is no longer relevant.
Comment 8 Philippe Le Hegaret 2015-06-16 20:38:47 UTC 
changed to WONTFIX to better reflect the resolution