Minutes from Pointer Events WG call 17 April 2019

Dear all, minutes from today's call (also available at 
https://www.w3.org/2019/04/17-pointerevents-minutes.html)

Pointer Events Working Group
17 Apr 2019
Attendees
Present
Regrets
Chair
Patrick H. Lauke
Scribe
Patrick H. Lauke
Contents
Topics
Summary of Action Items
Summary of Resolutions
<smaug> +present Olli_Pettay

<mustaq> +present mustaq

<NavidZ_> +present NavidZ

+present patrick_h_lauke

<scribe> Scribe: Patrick H. Lauke

NavidZ: now that Microsoft moved to Blink, what do we do regarding 
requiring having 3 separate implementations? Any news from Apple

Patrick: I've not heard anything from Apple, will ping them again (but 
they already have basic implementation in one of their tech previews)

NavidZ: UI Events are becoming more procedural (?) - do we need to make 
PE more procedural as well?

smaug: yes, do you know what status is?

NavidZ: will check what status is

<mustaq> NavidZ: Gary is making UI events spec procedural.

smaug: we should hook into that, will be useful for complex situations

NavidZ: next up, features we have proposed for v3

e.g. predicted points for drawing application (Microsoft had interest), 
coalesced events, pointerraw data

NavidZ: had some questions about privacy, and only exposing some API 
data under https

(e.g. exposing user has a 1000Hz mouse)

do we want to keep this sort of info to secure origin in coalesced and 
pointer raw

would like to get together and discuss, and wondering if Firefox have 
resources to implement some of this

smaug: we have some coalesced stuff already developed, raw data will be 
easy, predicted events will be more complex due to timing of events (at 
spec level we need to think about it more)

NavidZ: for predicted points, if anything is unclear, let's track on github

we're getting TAG review for v3, so we want to make sure everything is there

smaug: back to security, it's definitely something we need to look at

we need security folks to decide

will ask our security folks, other vendors will need to do same

<NavidZ_> privacy issue: https://github.com/w3c/pointerevents/issues/277

NavidZ: this sort of info has been exposed before on the web, but we 
should definitely tighten it

limit to secure origin, so can't be injected/accessed

want to make sure people are happy with this level of protection / flip 
the switch to make it only secure origin

should we do our bi-weekly (every 2 weeks) calls?

smaug: yes, sounds good, and this time would be perfect

NavidZ: Patrick can you follow up with Microsoft and Apple if they want 
to join call? (it's 8am in Seattle so should work for MS)

and do we want to meet F2F at TPAC

<smaug> looks like "leave meeting" doesn't work in any browser

(we check dates for next call - 1 May, so let's schedule next one for 4 
weeks time, 15 May)


-- 
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke

Received on Wednesday, 17 April 2019 16:00:21 UTC