15:03:06 RRSAgent has joined #pointerevents 15:03:06 logging to https://www.w3.org/2021/08/04-pointerevents-irc 15:04:10 Meeting: PEWG 15:04:40 Chair: Patrick H. Lauke 15:04:50 Agenda: https://lists.w3.org/Archives/Public/public-pointer-events/2021JulSep/0066.html 15:04:59 Scribe: patrick_h_lauke 15:05:03 present+ flackr 15:05:07 present+ smaug 15:05:15 present+ mustaq 15:05:20 present+ plh 15:05:25 present+ patrick_h_lauke 15:05:42 Topic: Expand note about preventing compatibility mouse events https://github.com/w3c/pointerevents/pull/403 15:08:15 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 15:09:08 I guess you can't hear me 15:09:17 let me rejoin 15:10:49 /me would like to come back to https://github.com/w3c/pointerevents/issues/384 if time allows 15:11:18 https://pr-preview.s3.amazonaws.com/w3c/pointerevents/pull/403.html#compatibility-mapping-with-mouse-events 15:13:35 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? 15:13:40 [group agrees] 15:13:50 ACTION: tweak the sentence to add [DOM], then merge 15:15:11 Topic: * Should "click", "dblclick" and "contextmenu" events be PointerEvents? https://github.com/w3c/pointerevents/issues/100 15:16:41 PAtrick: (explains issue history) made a first draft https://github.com/w3c/pointerevents/pull/404 15:19:19 Mustaq: we don't have anything normative in PE at the moment about CSSOM 15:19:31 Patrick: we do... https://w3c.github.io/pointerevents/#pointerevent-interface ... ah no you're right, it's in a note, so non-normative 15:19:44 Olli: we do need something normative... 15:20:15 Mustaq: do you mean we normatively need to define the exception, or the fact that regular PE have fractional coordinates? 15:21:01 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 15:22:44 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 15:23:12 Olli: [paraphrasing] but we do need to specify normatively for click etc for web compat 15:23:26 Olli's suggestion sounds good to me. 15:24:21 https://w3c.github.io/pointerevents/#pointerevent-interface 15:28:38 https://github.com/w3c/pointerevents/pull/404/files 15:29:46 [discussion on how to make the requirement normative] 15:30:16 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 15:31:45 Mustaq: suggest expanding the original note at end of 4.1 to say ... "except for click/auxclick/contextmenu and then link to this section" 15:35:08 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"? 15:35:35 Robert: i think SHOULD, but can live with MUST 15:36:06 Olli: I think it should be MUST 15:36:21 I am on the fence! 15:36:40 Patrick: ok, we lean towards MUST then, can change in future if UIEVENTS change (the CSSOM "patch" gets applied) 15:37:45 Patrick: mustaq can you live with MUST 15:37:48 Mustaq: yes 15:38:06 Patrick: and fundamentally it's for UIEVENTS to grapple with this, and once they do, we can change our spec 15:40:09 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 15:40:32 Patrick: one structural thin I noticed: when referencing {{PointerEvent}} in the markup, respec links to https://w3c.github.io/pointerevents/#dom-pointerevent 15:41:13 PAtrick: wondering if instead it should point to interface definition https://w3c.github.io/pointerevents/#pointerevent-interface 15:43:47 {{}} definition in Bikeshed here: https://tabatkins.github.io/bikeshed/#autolink-shortcuts 15:44:31 Better link: https://tabatkins.github.io/bikeshed/#autolinking 15:44:46 looking at the link to MouseEvent for instance in the note at end of 4.1, it goes to https://www.w3.org/TR/uievents/#mouseevent 15:46:41 [discussion about pros/cons] 15:46:59 Patrick: I might make the change in a separate self-contained PR, so we can back it out if it does cause issues/confusion 15:47:26 ACTION: change the PR to make second paragraph normative, expand original note at end of 4.1 15:49:05 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 15:49:24 rrsagent, create minutes 15:49:24 I have made the request to generate https://www.w3.org/2021/08/04-pointerevents-minutes.html Patrick_H_Lauke 15:49:28 FWIW, DOM spec was updated 2 days ago so I'll try to write a PR to fix https://github.com/w3c/pointerevents/issues/223 using the new hook in that spec. 15:49:39 rrsagent, set logs world-visible 15:49:50 thanks smaug 15:50:12 rrsagent, bye 15:50:12 I see 2 open action items saved in https://www.w3.org/2021/08/04-pointerevents-actions.rdf : 15:50:12 ACTION: tweak the sentence to add [DOM], then merge [1] 15:50:12 recorded in https://www.w3.org/2021/08/04-pointerevents-irc#T15-13-50 15:50:12 ACTION: change the PR to make second paragraph normative, expand original note at end of 4.1 [2] 15:50:12 recorded in https://www.w3.org/2021/08/04-pointerevents-irc#T15-47-26