Re: The semantics of touch-action: none. Propose change to touch-action: user

pointer-events: none is too broad. It means "don't do anything: no events,
no default gestures, nothing".


On Fri, Apr 19, 2013 at 5:30 PM, Benoit Marchant <marchant@mac.com> wrote:

> There's already pointer-event: none; implemented and used, which is
> amazingly well named in this context, what's the need to add something else?
>
> Benoit
>
> On Apr 19, 2013, at 17:11, Daniel Freedman <dfreedm@google.com> wrote:
>
> > Sorry for the really late thinking on this, but I've had some dev
> feedback about the semantics of touch-action that I had to share.
> >
> > In specific, touch-action: none is the oddity. The "none" value is
> confusing because it could be interpreted by the dev to mean "do no
> actions". It's about the only time I've seen a css property value that has
> such a different meaning when interpreted in the viewpoint of the browser
> or the developer.
> >
> > Instead, I propose that we rename "touch-action: none" to "touch-action:
> user", to make it explicit that the user now gets to handle the events
> instead of the browser.
> >
> > Thoughts?
>