Re: hit testing and retained graphics

On 7/6/11 7:33 PM, Tab Atkins Jr. wrote:
>> A way to force retained mode and hit testing would be to basically say that
>> in order to state that canvas is an element such that unless an author
>> creates a context, binds it to a separate fallback DOM object, applies a
>> bounding path, and applies a Z order that pointing events would not be
>> processed by the user agent on the canvas element. That would certainly
>> force the issue. I suspect you could keep most of the API you have.
>
> That won't work.  It makes it impossible to do reasonable things with
> canvas that need mouse interaction but *can't* reasonably map to an
> accessible subtree.

Indeed.  Another example is at http://sketch-a-char.kirelabs.org/

-Boris

Received on Thursday, 7 July 2011 03:34:48 UTC