14:56:08 <RRSAgent> RRSAgent has joined #pointerevents
14:56:08 <RRSAgent> logging to https://www.w3.org/2021/07/07-pointerevents-irc
14:56:51 <Patrick_H_Lauke> Meeting: PEWG
14:57:00 <Patrick_H_Lauke> Chair: Patrick H. Lauke
14:57:10 <Patrick_H_Lauke> Agenda: https://www.w3.org/events/meetings/9718517d-0e08-4377-bb7c-07332948233b/20210707T110000
14:57:23 <Patrick_H_Lauke> Scribe: Patrick_H_Lauke
15:00:30 <smaug> just a second
15:02:09 <Patrick_H_Lauke> currently being utterly confused by webex ... has the system changed?
15:02:49 <plh> plh has joined #pointerevents
15:04:15 <flackr> flackr has joined #pointerevents
15:04:20 <flackr> present+
15:04:20 <Patrick_H_Lauke> present+ smaug
15:04:25 <Patrick_H_Lauke> present+ flackr
15:04:30 <Patrick_H_Lauke> present+ plh
15:04:38 <Zakim> Zakim has joined #pointerevents
15:05:20 <Patrick_H_Lauke> present+ mustaq
15:06:16 <Patrick_H_Lauke> TOPIC: "Update targets of predicted and coalesced events when trusted event target changes." https://github.com/w3c/pointerevents/pull/390
15:08:40 <Patrick_H_Lauke> Patrick: i've seen some good comments, pull request was approved, but i wonder how this will square with the other PR https://github.com/w3c/pointerevents/pull/377 which essentially rips out the section you just updated Rob
15:10:50 <Patrick_H_Lauke> Patrick: what I would propose, in light of #377 which changes the whole section anyway, is not to spend time now refining this (for consistency etc) but get it out there into main branch, and THEN see how this affects #377 and if we can then put that into that one in some way
15:11:13 <Patrick_H_Lauke> [group agrees to merge now]
15:11:20 <Patrick_H_Lauke> ACTION: merge PR 390
15:12:17 <Patrick_H_Lauke> TOPIC: Review 'Update targets of predicted and coalesced events when trusted event target changes.' https://github.com/w3c/pointerevents/pull/390
15:12:56 <Patrick_H_Lauke> TOPIC: Review 'Expand explanation for non-coalesced events' https://github.com/w3c/pointerevents/pull/379 (in particular, use of "measurable" in the definition)
15:13:18 <Patrick_H_Lauke> https://github.com/w3c/pointerevents/pull/379
15:14:19 <Patrick_H_Lauke> Patrick: I know there's been approvals, but i wonder as we were going back and forth on "measurable" vs "continuous" if we can graft the two together https://github.com/w3c/pointerevents/pull/379#discussion_r665399239
15:16:17 <Patrick_H_Lauke> Patrick: think this is in line with what Rob was suggesting last time. is this a good idea? if so which variant? i think the first one ("continuous pointer sensor data") is closest to what Rob had in mind
15:16:27 <Patrick_H_Lauke> [group agrees first one is good]
15:17:02 <Patrick_H_Lauke> ACTION: Patrick to make change (add "continuous") and merge #379
15:18:13 <Patrick_H_Lauke> TOPIC: Review 'Simplify/clarify coalesced and predicted events' https://github.com/w3c/pointerevents/pull/377 
15:19:08 <Patrick_H_Lauke> Patrick: apologies, but even i have lost track now of where we are with this
15:20:33 <Patrick_H_Lauke> Mustaq: after Rob's change in the other PR, we had good separation between author-facing (10.1 / 10.2) and browser engineer facing (10.3)
15:20:46 <Patrick_H_Lauke> Patrick: and now in #377 10.3 doesn't exist anymore https://pr-preview.s3.amazonaws.com/w3c/pointerevents/pull/377.html
15:22:12 <Patrick_H_Lauke> Rob: where we introduce the concepts of coalesced and predicted events lists, we can put the bit about trusted events from the other PR
15:23:33 <Patrick_H_Lauke> Rob: do we have to do any modification of the list when getCoalescedEvents is called now? don't think we do, because it was only target that changes
15:25:03 <flackr> Could mention when target changes after dfn here https://github.com/w3c/pointerevents/pull/377/files#diff-0eb547304658805aad788d320f10bf1f292797b5e6d745a3bf617584da017051R969
15:25:55 <mustaq> https://pr-preview.s3.amazonaws.com/flackr/pointerevents/pull/390.html#populating-and-maintaining-the-coalesced-and-predicted-event-lists
15:28:21 <mustaq> After #390, both 10.1 and 10.2 are dev facing, while #10.3 is for browser engineers.  I prefer keeping 10.3 separate.
15:31:36 <Patrick_H_Lauke> Patrick: wondering if we keep 10.3, if there's anything that can still be salvaged with #377 ? might be easier to do a fresh PR that can then salvage any bits, but supersede #377
15:31:53 <Patrick_H_Lauke> Rob: might be worth making sure we talk about "trusted" events consistently
15:33:10 <Patrick_H_Lauke> [group agrees to supersede #377 and fresh PR]
15:33:38 <Patrick_H_Lauke> ACTION: Patrick to supersede #377 with fresh PR, still make sure it addresses issues it set out to close in #377
15:34:26 <Patrick_H_Lauke> TOPIC: Tweak the definition of coalesced event list to deal with untrusted events https://github.com/w3c/pointerevents/pull/391
15:35:10 <Patrick_H_Lauke> Patrick: unless somebody sees a problem with this, should we just merge?
15:35:16 <Patrick_H_Lauke> Rob: seems fine
15:36:04 <Patrick_H_Lauke> Olli: i'll write another matching one for predicted events
15:36:14 <Patrick_H_Lauke> Patrick: and i'll just merge when it comes in, if it's along same lines
15:36:20 <Patrick_H_Lauke> ACTION: Merge #391
15:36:41 <Patrick_H_Lauke> TOPIC: Unclear note about PointerEvent initialization of attributes to reflect coalesced events https://github.com/w3c/pointerevents/issues/374
15:38:27 <Patrick_H_Lauke> Patrick: I had an action from last time, clearly I haven't done anything, will do though
15:38:52 <Patrick_H_Lauke> Rob: we talked about maybe generalising to giving the idea that the event will contain everything author needs to know what changed since last event
15:39:05 <Patrick_H_Lauke> ACTION: Patrick to propose more generalised note
15:39:58 <smaug> https://github.com/w3c/pointerevents/issues/392
15:40:29 <Patrick_H_Lauke> TOPIC: How is pointer event ctor supposed to work when coalescedEvents is passed using the PointerEventInit https://github.com/w3c/pointerevents/issues/223
15:40:45 <Patrick_H_Lauke> Olli: filed a new DOM issue because i think we need a tweak at that spec to refer to it more easily
15:41:01 <Patrick_H_Lauke> once DOM spec is updated we can update PE spec
15:41:14 <Patrick_H_Lauke> TOPIC: HTML monkeypatching: initiate the drag-and-drop operation definition https://github.com/w3c/pointerevents/issues/384
15:41:40 <Patrick_H_Lauke> Mustaq: forgot, will do for next time
15:41:52 <Patrick_H_Lauke> ACTION: Mustaq to review issue #384
15:42:26 <Patrick_H_Lauke> TOPIC: Clarify whether touch contact must fire a pointerrawupdate event https://github.com/w3c/pointerevents/issues/373
15:42:50 <Patrick_H_Lauke> Patrick: these are my triage items, wondering if they can be closed or if there's actions that need to be taken
15:45:21 <Patrick_H_Lauke> Patrick: original poster then added info about their use case to https://github.com/w3c/pointerevents/issues/339
15:47:44 <Patrick_H_Lauke> ACTION: Close issue
15:47:46 <Patrick_H_Lauke> TOPIC: Immediately firing coalesced events for enter/leave/over/out? https://github.com/w3c/pointerevents/issues/278
15:48:30 <Patrick_H_Lauke> Olli: agree this can be closed
15:48:55 <Patrick_H_Lauke> Rob: agree, don't want this behaviour. this is specifically addressed by the work with did for target changes
15:49:07 <Patrick_H_Lauke> ACTION: Close #278
15:51:01 <mustaq> https://github.com/w3c/pointerevents/issues/100
15:52:18 <Patrick_H_Lauke> Mustaq: keep in mind for next meeting
15:52:41 <Patrick_H_Lauke> ACTION: Review issue #100 for discussion at next meeting
15:53:41 <Patrick_H_Lauke> rrsagent, set logs world-visible
15:54:17 <Patrick_H_Lauke> rrsagent, create minutes
15:54:17 <RRSAgent> I have made the request to generate https://www.w3.org/2021/07/07-pointerevents-minutes.html Patrick_H_Lauke
15:55:26 <Patrick_H_Lauke> rrsagent, bye
15:55:26 <RRSAgent> I see 9 open action items saved in https://www.w3.org/2021/07/07-pointerevents-actions.rdf :
15:55:26 <RRSAgent> ACTION: merge PR 390 [1]
15:55:26 <RRSAgent>   recorded in https://www.w3.org/2021/07/07-pointerevents-irc#T15-11-20
15:55:26 <RRSAgent> ACTION: Patrick to make change (add "continuous") and merge #379 [2]
15:55:26 <RRSAgent>   recorded in https://www.w3.org/2021/07/07-pointerevents-irc#T15-17-02
15:55:26 <RRSAgent> ACTION: Patrick to supersede #377 with fresh PR, still make sure it addresses issues it set out to close in #377 [3]
15:55:26 <RRSAgent>   recorded in https://www.w3.org/2021/07/07-pointerevents-irc#T15-33-38
15:55:26 <RRSAgent> ACTION: Merge #391 [4]
15:55:26 <RRSAgent>   recorded in https://www.w3.org/2021/07/07-pointerevents-irc#T15-36-20
15:55:26 <RRSAgent> ACTION: Patrick to propose more generalised note [5]
15:55:26 <RRSAgent>   recorded in https://www.w3.org/2021/07/07-pointerevents-irc#T15-39-05
15:55:26 <RRSAgent> ACTION: Mustaq to review issue #384 [6]
15:55:26 <RRSAgent>   recorded in https://www.w3.org/2021/07/07-pointerevents-irc#T15-41-52
15:55:26 <RRSAgent> ACTION: Close issue [7]
15:55:26 <RRSAgent>   recorded in https://www.w3.org/2021/07/07-pointerevents-irc#T15-47-44
15:55:26 <RRSAgent> ACTION: Close #278 [8]
15:55:26 <RRSAgent>   recorded in https://www.w3.org/2021/07/07-pointerevents-irc#T15-49-07
15:55:26 <RRSAgent> ACTION: Review issue #100 for discussion at next meeting [9]
15:55:26 <RRSAgent>   recorded in https://www.w3.org/2021/07/07-pointerevents-irc#T15-52-41