- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 3 Aug 2022 16:25:50 +0100
- To: Pointer Events Working Group <public-pointer-events@w3.org>
Dear all, with apologies for slipping up and nearly forgetting about this (hence the late confirmation email, which resulted in most people not knowing this was actually happening), the minutes from today's brief meeting are at https://www.w3.org/2022/08/03-pointerevents-minutes.html and copied below: PEWG 03 August 2022 Agenda https://www.w3.org/events/meetings/0d3af70c-0054-43dc-9c15-c60c5b9c3f3c/20220803T110000#agenda Present: mustaq, patrick_h_lauke Chair: Patrick H. Lauke Scribe: Patrick H. Lauke * Order of pointerover/enter/move and corresponding mouse events is different on browsers https://github.com/w3c/pointerevents/issues/454 * Heartbeat: Clarify what the target of the click event should be after capturing pointer events https://github.com/w3c/pointerevents/issues/356 * looking at the WPT Apologies. Clearly due to my getting mixed up with our fortnightly schedule and only sending the official confirmation/invite out just before the meeting... # Order of pointerover/enter/move and corresponding mouse events is different on browsers https://github.com/w3c/pointerevents/issues/454 Mustaq: a few cautions - why we don't have pointerout directly after mouseout Mustaq: suppose you have both a primary touch and mouse. browser can't make a sensible event flow Mustaq: can't have a direct mapping of pointerover/pointerout to mouseover/mouseout Mustaq: interleaving the events is the challenge Patrick: wondering if we should have some kind of sentence about browser only choosing a single primary to send compat events 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 <mustaq> Another related point: 11.1 says "user agents are encouraged to guarantee..." which is too vague for normative text, right? 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 Patrick: agree 11.1 needs to be solidified more... Mustaq: it definitely could do with a diagram perhaps to also explain Patrick: if you want to make a first rough stab at a diagram, I can then "prettify" it ACTION: Mustaq to look at 11.1, rough out a diagram, and Patrick to review # Heartbeat: Clarify what the target of the click event should be after capturing pointer events https://github.com/w3c/pointerevents/issues/356 Patrick: our standing item, no news at this point, but we'll review more closely at next meeting Mustaq: think we decided that click should go to capture item, and we have a few bugs around that # looking at the WPT Mustaq: [mentions Interop 2022 effort, finding gaps in coverage, would love to see some movement here as well] 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 -- Patrick H. Lauke https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Wednesday, 3 August 2022 15:26:06 UTC