14:54:45 <RRSAgent> RRSAgent has joined #pointerevents
14:54:45 <RRSAgent> logging to https://www.w3.org/2022/08/03-pointerevents-irc
14:56:19 <Patrick_H_Lauke> Meeting: PEWG
14:56:23 <Patrick_H_Lauke> Chair: Patrick H. Lauke
14:56:29 <Patrick_H_Lauke> Agenda: https://www.w3.org/events/meetings/0d3af70c-0054-43dc-9c15-c60c5b9c3f3c/20220803T110000#agenda
14:56:37 <Patrick_H_Lauke> Scribe: Patrick H. Lauke
14:56:43 <Patrick_H_Lauke> ScribeNick: Patrick_H_Lauke
15:05:41 <Patrick_H_Lauke> Apologies. Clearly due to my getting mixed up with our fortnightly schedule and only sending the official confirmation/invite out just before the meeting...
15:05:42 <mustaq> present+ Mustaq
15:05:50 <Patrick_H_Lauke> present+ mustaq
15:05:57 <Patrick_H_Lauke> present+ patrick_h_lauke
15:06:20 <Patrick_H_Lauke> Topic: Order of pointerover/enter/move and corresponding mouse events is different on browsers https://github.com/w3c/pointerevents/issues/454
15:07:29 <Patrick_H_Lauke> Mustaq: a few cautions - why we don't have pointerout directly after mouseout
15:08:47 <Patrick_H_Lauke> Mustaq: suppose you have both a primary touch and mouse. browser can't make a sensible event flow
15:09:37 <Patrick_H_Lauke> Mustaq: can't have a direct mapping of pointerover/pointerout to mouseover/mouseout
15:09:48 <Patrick_H_Lauke> Mustaq: interleaving the events is the challenge
15:12:26 <Patrick_H_Lauke> Patrick: wondering if we should have some kind of sentence about browser only choosing a single primary to send compat events
15:12:48 <Patrick_H_Lauke> Mustaq: but that brings problem that on desktop/laptop, mouse is always there, so can't just do it for the "first" primary it saw
15:15:22 <mustaq> Another related point: 11.1 says "user agents are encouraged to guarantee..." which is too vague for normative text, right?
15:15:47 <Patrick_H_Lauke> Patrick: so in general, i think we should reinforce the idea that yes, this aspect is a bit vague in the spec, because dealing with making a sensible mouse compat event stream is tricky particularly with multi-primary-pointer scenarios. and that authors should basically not try to rely on mouse compat events in these cases and go directly for pointer events
15:16:22 <Patrick_H_Lauke> Patrick: agree 11.1 needs to be solidified more...
15:16:47 <Patrick_H_Lauke> Mustaq: it definitely could do with a diagram perhaps to also explain
15:17:01 <Patrick_H_Lauke> Patrick: if you want to make a first rough stab at a diagram, I can then "prettify" it
15:17:44 <Patrick_H_Lauke> ACTION: Mustaq to look at 11.1, rough out a diagram, and Patrick to review
15:18:02 <Patrick_H_Lauke> TOPIC: Heartbeat: Clarify what the target of the click event should be after capturing pointer events https://github.com/w3c/pointerevents/issues/356
15:18:42 <Patrick_H_Lauke> Patrick: our standing item, no news at this point, but we'll review more closely at next meeting
15:19:03 <Patrick_H_Lauke> Mustaq: think we decided that click should go to capture item, and we have a few bugs around that
15:20:30 <Patrick_H_Lauke> TOPIC: looking at the WPT
15:20:57 <Patrick_H_Lauke> Mustaq: [mentions Interop 2022 effort, finding gaps in coverage, would love to see some movement here as well]
15:21:52 <Patrick_H_Lauke> Patrick: excellent, thank you for joining. We'll keep it short and sweet, but I'll make sure to set myself a proper alarm for the next meeting in 2 weeks' time
15:22:02 <Patrick_H_Lauke> rrsagent, set logs world-visible
15:22:07 <Patrick_H_Lauke> rrsagent, generate minutes
15:22:07 <RRSAgent> I have made the request to generate https://www.w3.org/2022/08/03-pointerevents-minutes.html Patrick_H_Lauke
15:22:14 <Patrick_H_Lauke> rrsagent, set logs world-visible
15:24:10 <Patrick_H_Lauke> rrsagent, bye
15:24:10 <RRSAgent> I see 1 open action item saved in https://www.w3.org/2022/08/03-pointerevents-actions.rdf :
15:24:10 <RRSAgent> ACTION: Mustaq to look at 11.1, rough out a diagram, and Patrick to review [1]
15:24:10 <RRSAgent>   recorded in https://www.w3.org/2022/08/03-pointerevents-irc#T15-17-44