Minutes from Pointer Events WG call 29 September 2021

Dear all,

minutes from today's call are at 
https://www.w3.org/2021/09/29-pointerevents-minutes.html and copied below:

29 September 2021


mustaq, Patrick_H_Lauke, smaug

Patrick H. Lauke

Patrick H. Lauke, Patrick_H_Lauke

# Notes with normative (SHOULD/MUST) statements 

Has a few pull requests from last meeting already, probably makes sense 
to review in order

* Make "Converting..." section normative 

Patrick: don't think we need to say anything about MUST/SHOULD implement 
both sets as it's implicit by being in the IDL

smaug: agree

mustaq: just worried developers might think, because they're 
complementary, they don't need to

smaug: i think because it's in the IDL it's clear it's a SHOULD/MUST

Patrick: happy to merge?

[no objections]

* Move elements of pointerId informative note to normative text 

mustaq: not sure if we need to be more precise with "existing pointers", 
as just saying it must not be influences by any other top-level browsing 
context is a bit a handwavy

smaug: it's a very dense sentence, but i think it's ok as is

[discussion on whether the now normative wording allows for mouse to 
always use same pointerId - it doesn't allow tracking across sites 
because it's the same, BUT the current wording doesn't seem to allow that]

mustaq: maybe we can leave it as is

smaug: needs some tweaking, but for now we can merge

mustaq: sorry, meant that we want to mention something about mouse

<mustaq> I meant adding the mouse case explicitly "has const id..."

Patrick: think bringing forward the bit about fingerprinting/tracking, 
so it's clearer why we do all that. mouse can be fixed, as you can't 
track across sites.

mustaq: we should mention that mouse pointer is special

Patrick: so how about also bringing forward the -1 value for 
non-pointer, then add something about UAs MAY reserve a pointerId for 
mouse. and then "for all other pointers, must be unique etc etc"

mustaq: we have the ask about pens being recognised

<mustaq> I now see "a particular pointing device for the lifetime of the 
page" already covers the removed pen case nicely.

Patrick: i'll make another stab at this

* Move first part of the note about dispatched event order into 
normative text https://github.com/w3c/pointerevents/pull/412

[discussion on whether first "should" should be a MUST, and the SHOULD 
should be a MUST as well]

mustaq: "should resemble" > "must match"

smaug: i think that captures it yes

<mustaq> Or "the UA must maintain the order..."

* Make note about UAs not firing compat events if they support touch 
events normative https://github.com/w3c/pointerevents/pull/413

smaug: i think the SHOULD NOT should be MUST NOT

mustaq: the last sentence about touch or pen worries me

Patrick: it's redundant now that i look at it. TE don't fire for mouse

Make note about buttons/buttons and compat events normative 

smaug: again, change SHOULD to MUST

since sending agenda i made two more PRs related to this

* Remove may/should from note about complex gestures 

still remains a note, just removes the trigger words may and should. 
doesn't change the meaning of what we're saying

smaug: this is fine

* Reword legacy properties note to remove the "must" 

<mustaq> https://bugs.chromium.org/p/chromium/issues/detail?id=692709#c5

Patrick: as this is about properties that we don't define in IDL, i 
personally don't care if some UA decides to keep those legacy things as 
long as it doesn't interfere

ACTION: make changes to the PRs as discussed, tackle the remaining ones 
in #405

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, 29 September 2021 16:33:43 UTC