W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2013

Re: [whatwg] Outline style to use for drawSystemFocusRing

From: Rik Cabanier <cabanier@gmail.com>
Date: Wed, 2 Oct 2013 18:37:06 -0700
Message-ID: <CAGN7qDBkZJEDTq1uahCWa4vo6KV+t4TyJixYRQUVrr7i_-D6Zg@mail.gmail.com>
To: Dominic Mazzoni <dmazzoni@google.com>
Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>, Ian Hickson <ian@hixie.ch>
Dominic,

it would be great if we could resolve this soon since I'm trying to land
this in mozilla and webkit.
I think the spec is good as-is, and Rich and Hixie (right?) believe so as
well.



On Mon, Sep 30, 2013 at 11:48 PM, Dominic Mazzoni <dmazzoni@google.com>wrote:

> On Mon, Sep 30, 2013 at 5:42 PM, Rik Cabanier <cabanier@gmail.com> wrote:
>
>> Where does it say in the spec that if you have assistive technology
>> enabled, focus rings should not be drawn?
>>
>
> if as a web author I call drawCustomFocusRing and it returns false, I'm
> not supposed to draw anything according to the spec. That's what doesn't
> make sense to me.
>
> It would take an element in fallback content as an argument. That would
>>> allow assistive technology to be notified.
>>>
>>
>> As Ian pointed out, the accessibility software could do that.
>>
>
> 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.
>
> If we added a canvas fallback element as a parameter to
> scrollPathIntoView, I don't think we'd need drawCustomFocusRing.
>
>
Received on Thursday, 3 October 2013 01:37:32 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:11 UTC