Re: Fw: Re: from Rik Cabanier on 2013-09-23 (public-html-a11y@w3.org from September 2013)

From: Rik Cabanier <cabanier@gmail.com>
Date: Mon, 23 Sep 2013 23:41:27 +0000
To: Dominic Mazzoni <dmazzoni@chromium.org>
Cc: Richard Schwerdtfeger <schwer@us.ibm.com>, Paul Cotton <Paul.Cotton@microsoft.com>, Janina Sajka <janina@rednote.net>, Steve Faulkner <faulkner.steve@gmail.com>, public-html-a11y@w3.org, jbrewer@w3.org, David Bolter <dbolter@mozilla.com>, Frank Olivier <franko@microsoft.com>, James Craig <jcraig@apple.com>
Message-ID: <CAGN7qDD17aWY936xbLqXRU_q7rNMnUqb=gPjgpEPOi7+5=8SoA@mail.gmail.com>

>From your email:

So, given that such a preference never exists, Chrome never draws anything
when you call drawCustomFocusRing. It just updates assistive technology and
returns false every time.

and reading the spec, it should return 'true' if the element is focused.

On Mon, Sep 23, 2013 at 9:20 AM, Dominic Mazzoni <dmazzoni@chromium.org>wrote:

> On Mon, Sep 23, 2013 at 8:04 AM, Rik Cabanier <cabanier@gmail.com> wrote:
>
>> Rich,
>>
>> yes, an API with the same name was implemented but it is not following
>> the spec.
>>
>
> Can you explain how it doesn't follow the spec? Do you mean that Chrome
> doesn't support a user preference for high-contrast focus rings? Or did we
> misinterpret some other aspect of the spec?
>
> - Dominic
>
>

Received on Tuesday, 24 September 2013 19:35:17 UTC