23979 2013-12-03 16:48:09 +0000 The differences between drawSystemFocusRing and drawCustomFocusRing should be better highlighted in the specification 2015-06-16 20:38:47 +0000 1 1 1 Unclassified HTML WG CR HTML Canvas 2D Context unspecified PC Windows NT RESOLVED WONTFIX a11y, a11y_canvas P2 major --- 1 plh dave.null mark.sadecki+w3c mike public-html-admin public-html-wg-issue-tracking schwer public-html-bugzilla oldest_to_newest 97059 0 plh 2013-12-03 16:48:09 +0000 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 97077 1 jaymunro 2013-12-03 21:28:46 +0000 reassigning to Canvas 2D Context Level 2 since drawSystemFocusRing and drawCustomFocusRing are at risk for CR. 97116 2 schwer 2013-12-04 14:36:28 +0000 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. 97149 3 jaymunro 2013-12-04 19:46:21 +0000 I jumped the gun on moving to L2, there are still ongoing discussions on the focus ring methods. Moving back to CR. 97231 4 mike 2013-12-06 06:58:36 +0000 (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. 97723 5 schwer 2013-12-16 23:52:23 +0000 move to L2 121123 6 plh 2015-06-16 20:27:24 +0000 Moved back to L1 121130 7 plh 2015-06-16 20:36:34 +0000 we now only have drawFocusIfNeeded, so this bug is no longer relevant. 121132 8 plh 2015-06-16 20:38:47 +0000 changed to WONTFIX to better reflect the resolution