- From: Tab Atkins <tabatkins@google.com>
- Date: Wed, 13 Feb 2013 13:51:13 -0800
- To: Alex Russell <slightlyoff@google.com>
- Cc: public-pointer-events@w3.org, Rick Byers <rbyers@google.com>
On Tue, Feb 12, 2013 at 7:27 AM, Alex Russell <slightlyoff@google.com> wrote: > The new touch-action CSS property seems to have conceptual overlap with the > pointer-events property. If nothing else, the naming (and explicit callout > to "touch" in the naming) creates huge ambiguity. Anyone who wants to allow > some clicks through, but not dragging, is likely to find themselves wading > through multiple properties who interaction is ambiguious at best. I haven't > though hard enough about this to know if the properties can (or should) be > merged, but it seems like an exercise the WG should attempt, if only to > identify a strong argument against merging them. They shouldn't be merged, as they do substantially different things. One controls what parts of the element are opaque/transparent to hit detection at all. The other controls, once a hit has been registered, what that hit should do. ~TJ
Received on Wednesday, 13 February 2013 21:51:41 UTC