- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 1 Jul 2011 13:14:02 -0700
- To: Charles Pritchard <chuck@jumis.com>
- Cc: Charles McCathieNevile <chaals@opera.com>, Matt May <mattmay@adobe.com>, Cameron McCormack <cam@mcc.id.au>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>, "public-html@w3.org" <public-html@w3.org>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>
On Fri, Jul 1, 2011 at 12:52 PM, Charles Pritchard <chuck@jumis.com> wrote: > Richard's proposals have described the secondary purpose of setElementPath as marshaling pointer events directly to the subtree where they would then bubble up as normal. This is constant with keyboard events bubbling up from the subtree. It's also controversial, as the elements in the subtree would retain path information to be used by the UA in delegation of onmouse and onclick events. Vendors would likely re-use hit testing from svg code paths. Hm, okay. How much of this is simple desire for hit-testing, and how much is actual desire to retarget clicks to the subtree? Just wanting to uncover the underlying problem that devs are trying to solve, so we can solve it well while still smuggling in accessibility. ~TJ
Received on Friday, 1 July 2011 20:14:50 UTC