- From: Michael[tm] Smith <mike@w3.org>
- Date: Mon, 30 Sep 2013 02:07:38 +0900
- To: Rik Cabanier <cabanier@adobe.com>
- Cc: "mark@w3.org" <mark@w3.org>, "schwer@us.ibm.com" <schwer@us.ibm.com>, "dbolter@mozilla.com" <dbolter@mozilla.com>, "dmazzoni@chromium.org" <dmazzoni@chromium.org>, "franko@microsoft.com" <franko@microsoft.com>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>, "janina@rednote.net" <janina@rednote.net>
Hi Rik, Rik Cabanier <cabanier@adobe.com>, 2013-09-29 09:51 -0700: > > It seems to me the reason for the renaming suggestion was not just to make > > it less confusing but because it's actually not itself drawing a custom focus > >ring at all, and is not even ensuring at all that one will actually be drawn. > > That's correct. This API is more like a question "Should the author draw a focus ring?" > However, it seems that this has been discussed quite a bit already and > it's been in the spec for years. Why pull it out/rename it now? Because it's not actually following the spec? > > Does that actually meet the original requirement that was stated for > > drawing custom focus rings, or is it doing something different? > > What is the original requirement? I assume it's what's defined for DrawCustomFocusRing in the current spec. > The APIs notify the accessibility code and optionally draw a ring. Is that exactly what the current spec says it should do? --Mike -- Michael[tm] Smith http://people.w3.org/mike
Received on Sunday, 29 September 2013 17:07:53 UTC