15:57:07 RRSAgent has joined #pointerevents 15:57:07 logging to https://www.w3.org/2022/03/02-pointerevents-irc 15:57:26 Meeting: PEWG 15:57:31 Chair: Patrick H. Lauke 15:57:44 Agenda: https://www.w3.org/events/meetings/0d3af70c-0054-43dc-9c15-c60c5b9c3f3c/20220302T110000 15:58:02 Scribe: Patrick H. Lauke 15:58:12 present+ Patrick_H_Lauke 16:00:16 flackr has joined #pointerevents 16:00:16 present+ smaug 16:00:21 present+ flackr 16:00:50 present+ Mustaq 16:01:59 TOPIC: Expand bullet about when pointercancel fires https://github.com/w3c/pointerevents/pull/434 16:02:28 Patrick: it's fairly minimal, but see if that covers what we need for now 16:02:33 Olli: I think that's fine 16:02:52 Robert: your example is very specific, but it's fine 16:03:33 Mustaq: as it's "for example", is that now non-normative? 16:04:06 Rob: normative point is still "when user agent determines there won't be more pointer events, send pointercancel", then we give examples 16:06:04 RESOLUTION: PR is ok to merge 16:06:39 TOPIC: Clarify which steps constitute canceling a pointer https://github.com/w3c/pointerevents/issues/400 16:06:50 Patrick: this is related to what we just discussed I think 16:07:38 Mustaq: I think Dominic asked originally https://github.com/w3c/pointerevents/issues/384#issuecomment-890219263 16:08:50 Rob: sounds reasonable, i guess we need to put a PR together for this 16:09:01 Patrick: do we have something similar already, in terms of structure, in our spec? 16:09:24 https://www.w3.org/TR/pointerevents/#process-pending-pointer-capture 16:09:25 Rob: there's process pending pointer capture 16:09:55 Rob: similar to what's asked here, describe steps for cancelation event, which we can then refer to from HTML spec 16:10:08 https://w3c.github.io/pointerevents/#process-pending-pointer-capture is the link to the latest version 16:10:36 Mustaq: making it more algorithmic 16:11:23 Patrick: should it be a sibling section to 5.1.3.2 ? 16:11:33 Mustaq: it might look weird because pointercancel is defined later 16:11:46 Rob: i think it's consistent though with the pointer capture 16:11:55 Mustaq: section further down can then refer to this 16:12:22 Patrick: volunteers to make an initial stab? 16:12:28 Mustaq: I can take a look 16:13:55 ACTION: Mustaq to draft PR for next meeting to add new section 5.1.3.2 Canceling pointer events (TBC) 16:14:29 Patrick: that would take care of issue 400. what's left... https://github.com/w3c/pointerevents/issues?q=is%3Aissue+is%3Aopen+label%3Av3 16:14:52 Olli: just reading https://github.com/w3c/pointerevents/issues/409 16:15:16 Olli: since we have clarified coalesced list prose quite a bit since then, wondering what's left 16:16:44 Olli: does spec say that for trusted event the list is NOT empty 16:17:46 https://w3c.github.io/pointerevents/#dfn-coalesced-events-list 16:19:00 Rob: so we need to add mention that the coalesced event list includes also the event itself that this was associated with 16:19:03 Olli: a clone of the event 16:19:21 Rob: the spec seems to already imply this, so maybe we just need an informative note rather than normative text 16:20:14 Olli: it doesn't need it for predicted events list 16:20:36 Mustaq: there's three bullets ("Monotonically..." etc). maybe we just add a bullet there 16:23:38 Patrick: the subject of that list is "the events", so wouldn't quite work. Maybe just extend the sentence that ends "the list is a sequence of all PointerEvents that were coalesced into this event" 16:23:50 Rob: this feels like we want both extending this, AND a note 16:24:03 Mustaq: yes, let's not overload this sentence 16:24:16 Olli: I guess I can try creating a PR for this 16:24:29 Patrick: that'd be cool, thank you 16:24:48 TOPIC: Relationship between main pointer event and coalesced events #409 16:26:15 ACTION: Olli to make draft PR to address issue 409 - extend sentence/section to cover coalesced events including the last raw event 16:26:38 Mustaq: i see we have respec errors in the spec 16:26:59 Patrick: yes relating to "you have definitions, but nothing links to them". in https://w3c.github.io/pointerevents/ github version 16:27:10 Patrick: i'll do a trawl through and see what needs correcting 16:30:15 Patrick: looking further, we have 2 more issues left relating to pointer capture. #356 and #357. last comment on #357 is that we'll park it until #356 is resolved. I see #356 is that dreaded "mouse on green/mouse on blue" one. I'd suggest for next time, we tackle the two PRs that we decided to do today, and then look at #356 16:30:38 Patrick: once #356 is then done, we can look further at #357. and then that clears our queue of v3 marked issues 16:31:30 Patrick: thank you all, stay safe 16:31:37 rrsagent, make logs world-visible 16:31:43 rrsagent, generate minutes 16:31:43 I have made the request to generate https://www.w3.org/2022/03/02-pointerevents-minutes.html Patrick_H_Lauke 16:31:50 rrsagent, make logs world-visible 16:32:01 rrsagent, bye 16:32:01 I see 2 open action items saved in https://www.w3.org/2022/03/02-pointerevents-actions.rdf : 16:32:01 ACTION: Mustaq to draft PR for next meeting to add new section 5.1.3.2 Canceling pointer events (TBC) [1] 16:32:01 recorded in https://www.w3.org/2022/03/02-pointerevents-irc#T16-13-55 16:32:01 ACTION: Olli to make draft PR to address issue 409 - extend sentence/section to cover coalesced events including the last raw event [2] 16:32:01 recorded in https://www.w3.org/2022/03/02-pointerevents-irc#T16-26-15