– DRAFT –
PEWG

continue harmonisation work PE spec (now that it includes mouse and wheel)

Patrick: from previous meeting, we agreed that using those tables we inherited from mouse/wheel for pointer as well is also a good idea

Rob: we talked about having one big table / possibly generating other tables from it

Patrick: what i've done so far is shorten the tables (removing everything that was repeated like clientX etc for every event) and i ported these naive tables to pointer events

<smaug> Just noting here. I think .relatedTarget and .composed should be defined for each event type

<flackr> I suggest we move click and other mouseevents which are pointerevents into the pointerevents section and mention in the mouseevents section that they are now pointerevents

Patrick: broad changes beyond that is i shortened the headings for all PE event types (not to be "The blah event" but just the event name itself, like mouse/wheel do)

Patrick: and I moved the "Examples" section (in current spec section3) to the end before security/privacy

<flackr> Bubbles for enter/leave is probably false

Patrick: so probably what we can do is do a bit of live debugging/coding now to make sure the tables i added (copy/pasted) are correct

<mustaq> https://w3c.github.io/pointerevents/#attributes-and-default-actions

Patrick: [added composed to all tables again, fixed up values for bubbles/cancelable/composed where needed]

<smaug> (https://mozilla.pettay.fi/composed-events-dispatch.html case C shows the composed + relatedTarget affecting event propagation, in case someone is interested in that :) )

[further live changes to things]

Patrick: if we continue work on this next time https://github.com/w3c/pointerevents/tree/patrickhlauke-harmonise-with-ui-events

Patrick: thank you all, let's continue with this (and in the meantime, feel free to grab this, open it locally, and hack away at it)

ACTION: continue work on harmonising the spec