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

Re: [pointerevents] Behaviour of dblclicks is not specified

From: lpd-au via GitHub <sysbot+gh@w3.org>
Date: Mon, 13 Nov 2017 08:52:35 +0000
To: public-pointer-events@w3.org
Message-ID: <issue_comment.created-343852011-1510563153-sysbot+gh@w3.org>
In addition to desktop touch, Chrome for Android seems to also fire `dblclick` events when the page isn't scrollable, ie a viewport is specified and the content fits on the screen. As Rick said, it doesn't fire otherwise. [The `touch-action` value seems to be irrelevant.](http://output.jsbin.com/rowuhe)

It seems sensible to me that adding a `dblclick` event handler would, if necessary to actually detect and fire the event, re-enable the (touch) click delay for that element and its descendents. And, likewise, that receiving such an event should only be guaranteed when `touch-action` is set to manipulation or stricter.

GitHub Notification of comment by lpd-au
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/171#issuecomment-343852011 using your GitHub account
Received on Monday, 13 November 2017 08:52:36 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 November 2017 08:52:37 UTC