W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2012

Re: [whatwg] canvas hitregion() clarification sought

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Wed, 25 Jul 2012 10:37:44 +0100
Message-ID: <CA+ri+VmP2oyfxdBLoahHdpqzdeWqxk5SDntgEGeKF0JX=chvQQ@mail.gmail.com>
To: whatwg <whatwg@whatwg.org>
resending as plain text as the first time the links made it indecipherable,

On 25 July 2012 01:13, Steve Faulkner <faulkner.steve@gmail.com> wrote:
>
> Upon reading the hit region section [1] of the spec again I noticed this:
>
> If any of the following conditions are met, throw a NotSupportedError
> exception and abort these steps.
> ...
> The arguments object's control member is not null but is neither an a
> element that represents a hyperlink, a button element, an input element
> whose typeattribute is in one of the Checkbox or Radio Button states, nor an
> input element that is a button
>
> This reads like it will throw an error if a custom control is referenced
> by control()
>
> <canvas>
>
> <div tabindex=0 role=checkbox>
>
> </canvas>
>
> is this correct?
>
> [1]
> http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#hit-regions
>
> --
> 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 Wednesday, 25 July 2012 09:39:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:09 GMT