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

[pointerevents] When to continue firing pointer events after a drag operation?

From: Stone via GitHub <sysbot+gh@w3.org>
Date: Tue, 03 Oct 2017 06:39:18 +0000
To: public-pointer-events@w3.org
Message-ID: <issues.opened-262319658-1507012744-sysbot+gh@w3.org>
mingchou has just created a new issue for https://github.com/w3c/pointerevents:

== When to continue firing pointer events after a drag operation? ==
Follow #194, spec says UA must fire pointercancel immediately before drag operation starts. Spec also says UA must also fire pointerout and pointerleave after pointercancel. But spec doesn't mention when to continue firing pointerevents (e.g. after drag operation ends or something). 

Tested with hoverable device, Chrome and Edge continue firing pointer events when the drag operation ends. But Chrome fires boundary events (pointerout, pointerleave, pointerover, pointerenter) when the drag operation ends, while Edge fires pointerout, pointerleave when drag operation starts and pointerover, pointerenter when drag operation ends.

Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/222 using your GitHub account
Received on Tuesday, 3 October 2017 06:39:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 3 October 2017 06:39:08 UTC