14:57:34 RRSAgent has joined #pointerevents 14:57:34 logging to https://www.w3.org/2021/07/21-pointerevents-irc 14:57:49 Meeting: PEWG 14:57:53 Chair: Patrick H. Lauke 14:57:59 Agenda: https://www.w3.org/events/meetings/9718517d-0e08-4377-bb7c-07332948233b/20210721T110000 14:58:12 Scribe: Patrick_H_Lauke 14:58:30 present+ Patrick_H_Lauke 15:02:12 flackr has joined #pointerevents 15:02:25 present+ flackr 15:03:05 present+ mustaq 15:03:37 TOPIC: Tweaks to coalesced/predicted events section https://github.com/w3c/pointerevents/pull/395 15:05:41 Patrick: i can make the change for "smaller than or equal" / "greater than or equal". The sanitisation one is trickier. 15:07:08 Rob: [paraphrasing] it gets complex if we expect to sanitize all passed untrusted events, with getters/setters/accessors, that can be observable 15:11:52 [discussing whether we want to have sanitisation or not - causes complications, and we already specifically say that other parts of the list management (e.g. monotonically ordered etc) only applies to trusted events] 15:13:16 Patrick: so is the minimum viable change here to add "trusted" to the start of 10.3 ? 15:13:20 Rob: yes 15:13:24 Patrick: I can make that change 15:13:49 mustaq: do we need to say anything about trusted events in other places, like 4.1.2 for instance which defines constraints for primary pointer? 15:14:48 mustaq: maybe we can do trusted here, and open a new issue to look at any other constraints to specify that it needs to be just for trusted 15:18:26 Patrick: what about the one instance where we ask UAs to sanitize tiltX/tiltY/azimuthAngle/altitudeAngle? 15:19:02 Rob: this is slightly different, as it backfills based on the dictionary/definition. doesn't do processing/sanitisation 15:19:27 mustaq: we also don't sanitise if developer has provided any value. this is only when they left them out completely 15:19:40 Patrick: yes, can rationalise that 15:20:31 ACTION: make the discussed changes and merge 15:20:49 TOPIC: Remove note about movementX/movementY and coalesced events https://github.com/w3c/pointerevents/pull/397 15:21:51 Patrick: I admit i can live with it as it is now, but it just strikes me that we say "this spec doesn't want to define this" and then goes on to strongly suggest what should happen 15:22:13 mustaq: agree with Patrick, but would be nice to link to PointerLock as reference 15:24:26 https://w3c.github.io/pointerlock/#extensions-to-the-mouseevent-interface 15:24:46 Rob: don't mind if we accept PR as is 15:25:44 mustaq: concerned that if we remove this, it's gone/not mentioned anywhere 15:26:31 Rob: in fairness, it's not about the non-coalesced events, but it's about the top level event itself 15:26:45 Rob: pointerlock spec can then refence the PE coalesced spec 15:26:52 ACTION: merge the PR 15:27:13 TOPIC: Should "click", "dblclick" and "contextmenu" events be PointerEvents? https://github.com/w3c/pointerevents/issues/100 15:28:39 Patrick: we mentioned click etc here https://w3c.github.io/pointerevents/#the-click-auxclick-and-contextmenu-events 15:30:22 Patrick: based on that, as developer, reading that click etc are PEs, i would then expect coordinates to have same precision 15:30:53 https://drafts.csswg.org/cssom-view/#extensions-to-the-mouseevent-interface 15:31:20 This is where they are re-defined as real numbers. 15:32:49 "The CCSOM View spec extensions don't apply to click, auxclick..." 15:34:40 Rob: looks like UIEvents specifies they're integers. if you look at 4.2.12 we reference UIEvents, so maybe we need to add a note "as the UIEvents spec defines these as integers...UAs MUST round these. even though type changes, precision hasn't." 15:34:49 mustaq: not even a note, and actual normative text 15:35:55 ACTION: Patrick to write additional text to define that click,aux,contextmenu despite being PEs must round their coordinates as per UIEvents spec 15:36:12 TOPIC: HTML monkeypatching: initiate the drag-and-drop operation definition https://github.com/w3c/pointerevents/issues/384 15:36:32 mustaq: forgot about this one 15:36:39 Patrick: don't worry, look at it for next time 15:36:55 ACTION: mustaq to review issue #384 and propose a change/addition 15:37:53 Patrick: just wanted to mention to that issues labelled v3 are slowly but steadily decreasing https://github.com/w3c/pointerevents/issues?q=is%3Aissue+is%3Aopen+label%3Av3 15:39:42 Patrick: some of those issues are likely hairy problems...but for now, I think it's good that we're making visible progress. I'd say unless there are other burning issues, we'll leave it at that and reconvene in 2 weeks' time. 15:39:50 rrsagent, set logs world-visible 15:39:58 rrsagent, create minutes 15:39:58 I have made the request to generate https://www.w3.org/2021/07/21-pointerevents-minutes.html Patrick_H_Lauke 15:40:12 rrsagent, set logs world-visible 15:40:17 rrsagent, bye 15:40:17 I see 4 open action items saved in https://www.w3.org/2021/07/21-pointerevents-actions.rdf : 15:40:17 ACTION: make the discussed changes and merge [1] 15:40:17 recorded in https://www.w3.org/2021/07/21-pointerevents-irc#T15-20-31 15:40:17 ACTION: merge the PR [2] 15:40:17 recorded in https://www.w3.org/2021/07/21-pointerevents-irc#T15-26-52 15:40:17 ACTION: Patrick to write additional text to define that click,aux,contextmenu despite being PEs must round their coordinates as per UIEvents spec [3] 15:40:17 recorded in https://www.w3.org/2021/07/21-pointerevents-irc#T15-35-55 15:40:17 ACTION: mustaq to review issue #384 and propose a change/addition [4] 15:40:17 recorded in https://www.w3.org/2021/07/21-pointerevents-irc#T15-36-55