- From: Geoffrey Sneddon via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Aug 2017 17:12:51 +0000
- To: public-pointer-events@w3.org
gsnedders has just created a new issue for https://github.com/w3c/pointerevents: == Difficulty understanding getCoalescedEvents definition == To me, the paragraph defining `getCoalescedEvents ` seems like a bit of mess. It makes a lot of statements without clearly delineating between them, and without defining what events get coalesced (and hence what properties they have are essentially undefined) and hence doesn't really define what the coalesced events even are. There's a bunch of sentences starting with conjunctions and similar adverbials ("also", "in addition", "so") which makes it seem like a list, except not all list items are preceded by them. I can make a guess that we're meant to create the coalesced events ordinarily and then just change various attributes, but that's not clear. Or are we not changing them because we've coalesced them in such a way that they've already got those values? I'd suggest something more like: > Returns a sequence of all PointerEvents that were coalesced into the dispatched pointermove event. > > Events must be coalesced into a single dispatched event grouped by [XXX], and the dispatched event's attributes set to a best representative summary of the coalesced events. > > Coalesced events must: > * have the same pointerId, pointerType, isPrimary, isTrusted, target as the dispatched event, > * have cancelable and bubbles set to false [NOTE: this is because they will never be dispatched], and > * have all attributes mutated during [event dispatch](https://dom.spec.whatwg.org/#concept-event-dispatch) set to their default value. [NOTE: all related functions, including `stopPropagation` and `stopImmediatePropagation`, will do nothing as a result] > > The sequence must be in chronological order, sorted by `timeStamp`. I think everything else in the paragraph is informative? You can add them back, but they should be clearly delineated from the normative requirements. Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/215 using your GitHub account
Received on Thursday, 10 August 2017 17:13:03 UTC