RE: Fw: [Bug 22803] Browser manufacturers request clarifying text for drawSystemFocusRing functions

> At TPAC, the at-risk list which contains the focus rings was accepted. Can you point me where that was rescinded?

I chaired the TPAC F2F meeting and I do NOT remember any such decision being made.  See the discussion on Canvas CR status in the F2F minutes:
http://www.w3.org/2013/11/14-html-wg-minutes.html#item13

In addition the HTML WG only makes decisions via a CfC on the Chairs have not yet issued such a CfC given that:

a) the A11Y TF Coordinators only ruled on the TF CfC on this topic on Dec 3:
http://lists.w3.org/Archives/Public/public-html-a11y/2013Dec/0006.html

b) at the Nov 21 TF meeting Philippe was asked to do research on possible bugs on  the drawSystemFocusRing  and drawCustomFocusRing methods and filed those bugs on Dec 3:
http://lists.w3.org/Archives/Public/public-html-a11y/2013Dec/0011.html

c) these bugs will be discussed at the A11Y TF scheduled for Dec 5 (tomorrow):
http://lists.w3.org/Archives/Public/public-html-a11y/2013Dec/0010.html

/paulc
HTML WG co-chair

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329

From: Rik Cabanier [mailto:cabanier@gmail.com]
Sent: Monday, December 02, 2013 6:28 PM
To: Richard Schwerdtfeger
Cc: Janina Sajka; public-html-a11y@w3.org
Subject: Re: Fw: [Bug 22803] Browser manufacturers request clarifying text for drawSystemFocusRing functions

Hi Rich,

I'm unsure what you are replying to.

On Mon, Dec 2, 2013 at 10:02 AM, Richard Schwerdtfeger <schwer@us.ibm.com<mailto:schwer@us.ibm.com>> wrote:

Rik,

I think the level of specificity that is being asked of browser manufacturers should apply to the rest of HTML5.

The browser manufacturers have asked for additional specifics around scrolling and hit testing that is not documented elsewhere in the HTML5 spec. This would indicate that an inconsistency in how the browsers handle these features across browsers. ... For example, when is an HTML element considered scrolled out of view, obscured and does not respond to hit testing. Where does the HTML5 spec. discuss scrolling and position of HTML objects?  IOW if you need this level of specificity then we should take HTML5 back to last call or make it such that we add this special case level of specificity and get it into Canvas 1.0.

The "scrolling into view" of the focus ring is not about hit testing. It's about what happens when you 'tab' to an element that is currently outside of the view. All browsers currently scroll the page so it goes into view and I believe that the element in the canvas shadow DOM should do the same.

Also, you moved this to not a CR issue when Janina asked that we try to make the corrections as part of the 1.0 version of canvas.

When did this happen?
At TPAC, the at-risk list which contains the focus rings was accepted. Can you point me where that was rescinded?


-----Forwarded by Richard Schwerdtfeger/Austin/IBM on 12/02/2013 11:50AM -----
To: Richard Schwerdtfeger/Austin/IBM@IBMUS
From: bugzilla@jessica.w3.org<mailto:bugzilla@jessica.w3.org>
Date: 12/01/2013 04:15PM
Subject: [Bug 22803] Browser manufacturers request clarifying text for drawSystemFocusRing functions
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22803

rcabanie <cabanier@adobe.com<mailto:cabanier@adobe.com>> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cabanier@adobe.com<mailto:cabanier@adobe.com>
          Component|CR HTML Canvas 2D Context   |CR HTML5 spec
           Assignee|jaymunro@microsoft.com<mailto:jaymunro@microsoft.com>      |robin@w3.org<mailto:robin@w3.org>

--- Comment #3 from rcabanie <cabanier@adobe.com<mailto:cabanier@adobe.com>> ---
Removing CR status as this feature is on the at-risk list and will be removed
from the first level

--
You are receiving this mail because:
You reported the bug.