W3C home > Mailing lists > Public > public-canvas-api@w3.org > July to September 2011

Re: hit testing and retained graphics

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Fri, 1 Jul 2011 10:48:02 +0100
Message-ID: <BANLkTi=zwxcgTokTvL2aVgyqrSN0OD3K5Q@mail.gmail.com>
To: Richard Schwerdtfeger <schwer@us.ibm.com>
Cc: chuck@jumis.com, franko@microsoft.com, Mike@w3.org, david.bolter@gmail.com, cyns@exchange.microsoft.com, public-canvas-api@w3.org, public-html-a11y@w3.org, public-html@w3.org
hi all
some more  examples:


On 17 June 2011 19:41, Richard Schwerdtfeger <schwer@us.ibm.com> wrote:

>  Charles, Frank, Mike,
> I am back from vacation. How far do we need to go with hit testing? Right
> now I am looking at associating a closed draw path with a DOM object in the
> canvas subtree. We would then need to address the routing of pointing device
> input events to the DOM object. The drawing path can be used to provide
> bound information to platform accessibility API.
> Do we need to bind any other drawing properties to the canvas object -
> similar to the way device context's are handled on graphic subsystems like
> Windows?
> Mike, I am including you as before I went on vacation you indicated that a
> number of developers desired this feature and wanted to be involved.
> Rich
> Rich Schwerdtfeger
> CTO Accessibility Software Group

with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
HTML5: Techniques for providing useful text alternatives -
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Friday, 1 July 2011 09:48:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:10:31 UTC