20240 2012-12-04 19:00:57 +0000 Pointer Event and Click 2012-12-04 19:03:03 +0000 1 1 1 Unclassified PointerEventsWG Pointer Events specification unspecified PC Windows NT RESOLVED WORKSFORME P2 normal --- 1 jrossi jrossi public-pointer-events public-pointer-events-bugzilla oldest_to_newest 79427 0 jrossi 2012-12-04 19:00:57 +0000 From: Daniel Freedman <dfreedm@google.com> Date: Thu, 29 Nov 2012 16:21:49 -0800 Message-ID: <CAAUAVAhuTu+eeOoah1hM7k334xwo3mPcVEavx4eubsSJipb_eA@mail.gmail.com> To: public-pointer-events@w3.org Hi, I'm working on a PointerEvents polyfill and I've run into an odd note in the spec. In section 7, click is explicitly excluded from the compatibility mouse events, leaving no good way to control the generation of click events. This brings to mind a few issues: 1. If a developer uses pointerdown.preventDefault, they could receive click events without a mousedown/mouseup. This seems very strange. 2. There are cases in which a developer would want to conditionally react to a click based on pointer movement. If the click event cannot be prevented by pointermove, the only option is to try and prevent the next click, which has potential for buggy interaction. 3. If click events are not provided by the browser, developers will try to make their own with pointerdown/up pairs, which is wasted effort. 4. Touch Events provide the ability to control click event generation, and developers familiar with that system will understand how it behaves. With these points in mind, would it be possible to add the control of click events to Pointer Events? Thanks 79428 1 jrossi 2012-12-04 19:03:03 +0000 This issue was resolved on the mailing list: http://lists.w3.org/Archives/Public/public-pointer-events/2012OctDec/0078.html http://lists.w3.org/Archives/Public/public-pointer-events/2012OctDec/0089.html From: Daniel Freedman [mailto:dfreedm@google.com] Sent: Monday, December 3, 2012 2:45 PM To: Scott González Cc: Jacob Rossi; public-pointer-events@w3.org Subject: Re: Pointer Events and click 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!