[Bug 23979] The differences between drawSystemFocusRing and drawCustomFocusRing should be better highlighted in the specification

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23979

--- Comment #4 from Michael[tm] Smith <mike@w3.org> ---
(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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 6 December 2013 06:58:37 UTC