- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 5 Feb 2020 16:35:44 +0000
- To: public-pointer-events@w3.org
Dear all, minutes from today's call are available on https://www.w3.org/2020/02/05-pointerevents-minutes.html and copied below: Pointer Events Working Group 05 Feb 2020 Agenda https://lists.w3.org/Archives/Public/public-pointer-events/2020JanMar/0004.html Attendees Present smaug, patrick_h_lauke, NavidZ Regrets Chair Patrick H. Lauke Scribe Patrick H. Lauke Patrick: this is likely going to be a short call. not going to work through all remaining open issues one by one here without prior preparation, and apologies for the haphazard lack of planning due to lots of work commitments on my side that left me unable to do anything for W3C hoping this will be start, a heartbeat to see what we need to do going forward NavidZ: question is if we have any more significant work for v3. as microsoft had some thoughts on inking/trails, but question is if we can add it to PEv3 or if it's outside charter Patrick: it was my recollection that there were no further significant things, and agree that inking/trailing may be out of scope Navid: if we look over open issues with v3, we still have the question about updating click/doubleclick/context as pointer events we did some tests, we would like to get this resolved for keyboard interaction, we decided to use an invalid pointerId as PE we're dependent on UI events, so quesiton is what we should do Olli: have you discussed with Gary? Navid: discussed with Gary and Travis at TPAC, and they'd be ok with it, but question is where we change things...in PE or in UI events I can hash out the details and come up with more of a plan Microsoft had strong views in favour of it, but there were some open questions Could implement but not enable as default Olli: would be good to get more data on where it can cause problems, particularly since coordinates are upgraded from integer to fractional Navid: i'll take action to put pull request out for the the issue and hopefully we'll get feedback apart from that, the issue of having both tilt properties (to include angles like Webkit does) Patrick: admittedly my fault for sending out notice late, i apologise. i would suggest beyond these, if we take time in the next two weeks before next meeting to go over remaining open issues and see what can be quickly addressed, maybe just with editorial tweaks, or what might require deeper discussion, and we take it from there in two weeks time to hopefully whittle down remaining open issues Navid: for the tilt, we need to pin down exactly what we want to do, if we should rely on libraries or similar, just so we can decide how/what to implement in browser ... I'll take action to write PR for click/context/doubleclick and Patrick if you could look at the tilt X/Y thing that would be good Patrick: i lost track, but how are PE in Firefox now? enabled by default Olli: enabled for a long time now in desktop and mobile browser <smaug> (new version of mobile FF. Firefox preview or whatever it might be on Play) Navid: do we know anything about Safari? they fail quite a few of the tests. Chrome does as well, so we probably need to sort some things out at our end, but we should see what Safari's intentions are Patrick: not heard anything directly, I know Philippe tried to get folks from Apple to engage with the WG, but so far I don't think there's desire or it's high on their priority list. Navid: I'm sure we can reach out more directly to some folks on the Safari team to see what their thinking is. In meantime would be good to go over tests again and see where possible gaps are. Patrick: so once again apologies for the haphazard last minute organisation on this. Hoping that going forward I will have appropriate time carved out to look at this in a more timely manner, but feel free to kick me if I don't. We reconvene in 2 weeks' time, where we'll look over specific issues that are still open. it does feel like we're close to having v3 as complete as we wanted to make it at this stage. in future, it may wel l be that the spec may be merged into a more general events spec and further work carried out there, rather than being something separate. we'll see. <scribe> ACTION: Navid to look at PR for the click/context/double click issue https://github.com/w3c/pointerevents/issues/100 <scribe> ACTION: Patrick to look at tiltX/tiltY https://github.com/w3c/pointerevents/issues/274 and how we could include both types of values/coordinates <scribe> ACTION: all to review any outstanding open issues and to pick a few high-profile ones to triage/discuss https://github.com/w3c/pointerevents/issues?page=1&q=is%3Aissue+is%3Aopen (suggest in run-up to next meeting) Summary of Action Items [NEW] ACTION: all to review any outstanding open issues and to pick a few high-profile ones to triage/discuss https://github.com/w3c/pointerevents/issues?page=1&q=is%3Aissue+is%3Aopen (suggest in run-up to next meeting) [NEW] ACTION: Navid to look at PR for the click/context/double click issue https://github.com/w3c/pointerevents/issues/100 [NEW] ACTION: Patrick to look at tiltX/tiltY https://github.com/w3c/pointerevents/issues/274 and how we could include both types of values/coordinates -- 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, 5 February 2020 16:35:52 UTC