W3C home > Mailing lists > Public > public-pointer-events@w3.org > October to December 2012

Re: Pointer Events and click

From: Daniel Freedman <dfreedm@google.com>
Date: Mon, 3 Dec 2012 14:45:20 -0800
Message-ID: <CAAUAVAhvUFC1yK8d6CBLdwWsrO=ng5F-BAskH6O4+8wgELxZXQ@mail.gmail.com>
To: Scott González <scott.gonzalez@gmail.com>
Cc: Jacob Rossi <Jacob.Rossi@microsoft.com>, "public-pointer-events@w3.org" <public-pointer-events@w3.org>
Hmm, I realize now that all the use cases I had thought of are really
"gesture" related, and would thus fall out of scope.
The arguments about why preventDefault() only stops mouse* events makes
sense, and that preventDefault pointerdown will prevent the defaults of
mousedown as well is good to know.

Thanks!

On Mon, Dec 3, 2012 at 5:10 AM, Scott González <scott.gonzalez@gmail.com>wrote:

> On Sun, Dec 2, 2012 at 6:27 PM, Jacob Rossi <Jacob.Rossi@microsoft.com>wrote:
>
>> " There are cases in which a developer would want to conditionally react
>> to a click based on pointer movement" sounds to me like the uses cases
>> delve into gesture recognition, which is out of scope for our charter.
>
>
> I don't have a major concern either way, but I just wanted to note a case
> in jQuery UI where we care about conditionally forcing a click based on
> pointer movement, but we don't actually care about gestures. We have a
> button widget which can build on top of various markup. When applied to a
> checkbox or radio, we visually hide the form control and style the label.
> Browsers generally have some tolerance for movement during a click. At
> least in Firefox, there is a noticeable difference in the tolerance allowed
> when clicking on a checkbox vs. clicking on a label associated with a
> checkbox. This is likely to make text selection of the label prevent
> toggling the checkbox. However, since we're treating the label as a button,
> we're not concerned with text selection and would like the larger movement
> tolerance that comes with the form control itself. The only way to work
> around this is to listen to mousedown/up and then check if a click or
> change event occurred on the checkbook and if not manufacture one.
>
> I believe this is the only place in jQuery UI where we conditionally care
> about clicks based on movement, so I don't have strong feelings either way.
> I do agree with everything else Jacob has said. In general, I don't think
> we should use "developers are familiar with X from Touch Events" as a
> strong argument for anything in Pointer Events as the majority of
> developers are not familiar with Touch Events and many that are familiar
> with them have complaints about them.
>
Received on Monday, 3 December 2012 22:46:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:24 UTC