15:00:47 RRSAgent has joined #pointerevents 15:00:47 logging to https://www.w3.org/2021/05/12-pointerevents-irc 15:01:01 Meeting: PEWG 15:01:05 Chair: Patrick H. Lauke 15:01:09 a bit late... 15:01:12 Agenda: https://www.w3.org/events/meetings/9718517d-0e08-4377-bb7c-07332948233b/20210512T110000 15:01:28 Scribe: Patrick_H_Lauke 15:03:18 flackr has joined #pointerevents 15:03:21 present+ 15:03:29 present+ smaug 15:04:07 plh has joined #pointerevents 15:05:30 present+ plh 15:05:49 Topic: Final review of 'Add new section explaining coalesced and predicted events' https://github.com/w3c/pointerevents/pull/364 15:12:48 Patrick: did everybody have chance to review? any outstanding concerns 15:13:01 [No concerns noted] 15:13:19 Action: will merge this after the meeting (once approval on the PR etc has been sorted out) 15:13:40 Topic: Final review of 'Major refactoring: refer to "direct manipulation" rather than "touch"' https://github.com/w3c/pointerevents/pull/350 15:17:45 Patrick: have you all had a chance to give one final look over this? It has not changed since last meeting (after the last change of "scrolling" to "panning" was made). still has a few instances of the word "scrolling", but only in contexts where it made sense (in an explanation, or when giving an example) 15:18:14 Olli: i looked over at the time, would like to go over again. [after reading over it] Yeah I think it looks fine 15:20:16 Patrick: so if i merge after the meeting, we happy? 15:20:19 [group agrees] 15:20:34 Action: merge after the meeting 15:21:36 Topic: "Should events queue a task?" https://github.com/w3c/pointerevents/issues/197 15:23:39 Olli: is this not a UI events issue? 15:24:05 Patrick: i see a reference to https://github.com/w3c/uievents/issues/23 which is from 2015, and has a "NeedsAlgorithm" label 15:24:25 Rob: should we not clarify when events fire? 15:24:33 Olli: but that is implementation-dependent 15:25:51 Patrick: should i close this? 15:26:08 Olli: we might want to keep it around until it's resolved...somewhere else 15:26:23 Patrick: happy to keep open, but label as "Future", so it's clear it's not v3-blocking 15:26:50 Olli: it might impact pointerraw events, as they will then need to align 15:26:54 Rob: fair enough 15:27:09 Action: keep issue open, mark as "Future" 15:28:49 Topic: "How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit" https://github.com/w3c/pointerevents/issues/223 15:32:43 [some initial discussion] 15:33:01 Olli: the core issue is that we don't define what happens when you call the constructor of the event 15:33:09 Rob: it should just...set the list 15:33:34 Patrick: so we just need to add some text in the new (from the other PR) section 15:37:14 https://dom.spec.whatwg.org/#constructing-events 15:39:40 Patrick: as my brain isn't grokking this, mind if I assing this to you to have a look at what we might need to add to our spec? 15:39:53 Olli: yes, I can ask AVK what the best way to go about this is 15:40:11 Rob: we have something related in the web animations API that might be useful to look at 15:40:37 Action: Assign issue to Olli for initial check of what needs to be added to PE spec 15:41:23 [Rob points to keyframe event as a similar example] 15:42:51 Topic: "This API always returns at least one coalesced event for pointermove events and an empty list for other types of PointerEvents." https://github.com/w3c/pointerevents/issues/224 15:44:08 Rob: i think issue here is what you get from coalesced event list is what you get from construction, but we have somewhere else that getcoalesced event returns at least one event 15:44:16 Olli: let me see, this was filed so long ago 15:44:36 Olli: yeah the text has changed since then 15:44:47 https://w3c.github.io/pointerevents/#dfn-coalesced-event-list 15:46:44 Olli: maybe it needs some clarification that "if this was a user agent created event, then ... ", as we want to differentiate JS-created events 15:47:08 +1 15:47:34 Patrick: so after merging the PR for the new section, can we bash out some clarifying text in the issue discussion itself? 15:47:38 Olli: +1 15:47:48 Olli: and it depends on the constructor issue 15:48:59 Action: for next time, Olli et al to come up with proposed addition to spec from discussion in https://github.com/w3c/pointerevents/issues/224 15:51:02 Patrick: that gets to the end of what I had earmarked. If there's no other business, let's reconvene in 2 weeks' time. 15:51:11 rrsagent, set logs world-visible 15:51:19 rrsagent, create minutes 15:51:19 I have made the request to generate https://www.w3.org/2021/05/12-pointerevents-minutes.html Patrick_H_Lauke 15:51:55 rrsagent, bye 15:51:55 I see 5 open action items saved in https://www.w3.org/2021/05/12-pointerevents-actions.rdf : 15:51:55 ACTION: will merge this after the meeting (once approval on the PR etc has been sorted out) [1] 15:51:55 recorded in https://www.w3.org/2021/05/12-pointerevents-irc#T15-13-19 15:51:55 ACTION: merge after the meeting [2] 15:51:55 recorded in https://www.w3.org/2021/05/12-pointerevents-irc#T15-20-34 15:51:55 ACTION: keep issue open, mark as "Future" [3] 15:51:55 recorded in https://www.w3.org/2021/05/12-pointerevents-irc#T15-27-09 15:51:55 ACTION: Assign issue to Olli for initial check of what needs to be added to PE spec [4] 15:51:55 recorded in https://www.w3.org/2021/05/12-pointerevents-irc#T15-40-37 15:51:55 ACTION: for next time, Olli et al to come up with proposed addition to spec from discussion in https://github.com/w3c/pointerevents/issues/224 [5] 15:51:55 recorded in https://www.w3.org/2021/05/12-pointerevents-irc#T15-48-59