W3C home > Mailing lists > Public > public-html@w3.org > March 2012

Re: ISSUE-201: canvas-fallback - Chairs Solicit Alternate Proposals or Counter-Proposals

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Fri, 30 Mar 2012 11:39:17 +0100
Message-ID: <CA+ri+VkJORw0Et2DCgHrHFdECp50-EjMv0P4RuorevOQbWXA-Q@mail.gmail.com>
To: "Edward O'Connor" <eoconnor@apple.com>
Cc: public-html@w3.org
Hi Ted,

I would be appreciative if you could provide in your change proposal,
rationale and any details of how this aspect of hixie's hitregion() may be
implemented to hook up with accessibility APIs:

An unbacked region description consists of the following:

   -

   Optionally, a label.
   -

   An ARIA role, which, if the unbacked region
description<http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#hit-region%27s-unbacked-region-description>also
has a label, could be the empty string.


I have asked on the wiki and mailing list,but hixie has not provided
anything so far.

regards
Stevef


On 21 March 2012 23:12, Edward O'Connor <eoconnor@apple.com> wrote:

> Hi,
>
> Maciej wrote, on behalf of the chairs:
>
> > 'Provide canvas location and hit testing capability to fallback
> > content'
> > The current status for this issue:
> >
> > http://www.w3.org/html/wg/tracker/issues/201
> > http://dev.w3.org/html5/status/issue-status.html#ISSUE-201
> >
> > So far, we have one Change Proposal submitted:
> >
> > http://www.w3.org/wiki/Canvas_hit_testing
> >
> > At this time the Chairs would also like to solicit additional Change
> > Proposals (possibly with "zero edits" as the Proposal Details), in case
> > anyone would like to advocate the status quo or a different change than
> > the specific one in the existing Change Proposals.
>
> I volunteer to write an alternate Change Proposal for this issue.
>
> Hit testing functionality in <canvas> can best be provided by an exposed
> Path object API such as the one recently added to the Editor's Draft.
> I've advocated for this in the past in this WG, and I welcome the
> editor's recent work in this area. That said, the Path API is very new
> and I've been using my HTML WG time to work on Change Proposals for
> other issues, so I'll need some time to write up rationale for the
> recent API additions.
>
> I have a CP for ISSUE-200 due next week, and I've just asked for an
> extension to the week after that for ISSUE-194. If the chairs could give
> me until the subsequent week (Wednesday 11 April, if I'm doing the math
> right) to produce a CP for ISSUE-201, I would be very grateful.
>
>
> Thanks,
> Ted
>
>


-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Friday, 30 March 2012 10:40:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:47 GMT