Meeting minutes
Expand note about preventing compatibility mouse events https://github.com/w3c/pointerevents/pull/403
Patrick: setting scene, this is out of me being surprised by passive events not being able to prevent mouse compat. agree that it's kind of repeating things if you know DOM events, but maybe we can strike balance of just mentioning it for noobs like me who are not as familiar
<smaug> I guess you can't hear me
<smaug> let me rejoin
<plh> /me would like to come back to https://
Patrick: i'll add extra bit to the sentence to make it clear those two links point to [DOM] spec, and then we happy to merge?
[group agrees]
Action: tweak the sentence to add [DOM], then merge
* Should "click", "dblclick" and "contextmenu" events be PointerEvents? https://github.com/w3c/pointerevents/issues/100
PAtrick: (explains issue history) made a first draft https://
Mustaq: we don't have anything normative in PE at the moment about CSSOM
Patrick: we do... https://
Olli: we do need something normative...
Mustaq: do you mean we normatively need to define the exception, or the fact that regular PE have fractional coordinates?
Olli: there's no compat problem whether browsers use fractional or not for regular PEs, it's only in this case with the click/auxclick/contextmenu that we do need to normatively make a statement for webcompat reasons
Patrick: if a UA doesn't use CSSOM fractional coords for regular pointer events (as it's not normative currently), then they would not hit the problem for click etc either, or rather they'd automatically satisfy this
Olli: [paraphrasing] but we do need to specify normatively for click etc for web compat
<mustaq> Olli's suggestion sounds good to me.
<flackr> https://
https://
[discussion on how to make the requirement normative]
Patrick: could remove the first para in that note, keep the second para but remove the note markup around it, so that second para remains there and is normative
Mustaq: suggest expanding the original note at end of 4.1 to say ... "except for click/auxclick/contextmenu and then link to this section"
Patrick: SHOULD or MUST? this may change in future, developers may even moan in future about "to get fractional, i have to listen to pointerup rather than click"?
Robert: i think SHOULD, but can live with MUST
Olli: I think it should be MUST
<mustaq> I am on the fence!
Patrick: ok, we lean towards MUST then, can change in future if UIEVENTS change (the CSSOM "patch" gets applied)
Patrick: mustaq can you live with MUST
Mustaq: yes
Patrick: and fundamentally it's for UIEVENTS to grapple with this, and once they do, we can change our spec
Patrick: other point: should mouse compat mention this too? (thinks about this some more) ah no because if a UA decides to fire these, they are intrinsically MouseEvents, so no "conversion" or change needed
Patrick: one structural thin I noticed: when referencing {{PointerEvent}} in the markup, respec links to https://
PAtrick: wondering if instead it should point to interface definition https://
<mustaq> {{}} definition in Bikeshed here: https://
<mustaq> Better link: https://
looking at the link to MouseEvent for instance in the note at end of 4.1, it goes to https://
[discussion about pros/cons]
Patrick: I might make the change in a separate self-contained PR, so we can back it out if it does cause issues/confusion
Action: change the PR to make second paragraph normative, expand original note at end of 4.1
Patrick: looking at time, probably not worth starting new topic. would say we end it early now, and catch up again in 2 weeks' time. thanks all