W3C

- DRAFT -

PEWG

30 Oct 2019

Agenda

Attendees

Present
patrick_h_lauke, NavidZ, Olli_Pettay
Regrets
Chair
Patrick H. Lauke
Scribe
Patrick H. Lauke

Contents


<scribe> Scribe: Patrick H. Lauke

we added the coalesced and pointerraw to the main spec; we have a PR for the predicted events to be added to the spec, which just needs a few minor edits

NavidZ: if Olli could take a look at the PR, then we can merge it
... once that is merged we can remove the extension document

after that, we can do the web platform tests as well

Olli: I've added myself as reviewer

NavidZ: after removing these are we good to proceed?

Patrick: yes i think once we merged this, we can leave the open issues in github as they're mostly refinements, and go for FPWD which i know philippe is keen on

NavidZ: do we need 3 implementations?

Olli: FPWD doesn't need implementations

Patrick: correct

NavidZ: what's the status on predicted and coalesced in other platforms?

Olli: we have something working for coalesced, nothing yet for predicted

what's Chrome doing for predicted?

NavidZ: Chrome currently not doing anything specific for predicted (?)

we're experimenting with predictors, doing the same for scrolling too

later we can take advantage of prediction available on platform but we're not there yet

we're almost there in terms of merging. want to set timeline

get document ready for next meeting in two weeks time. Navid will be at BlinkOn but we can have everything ready.

Patrick: will try to get other parts done, such as going over privacy implications of new APIs that expose potentially more info about user. then will get in touch with PLH to see what the formal steps for FPWD are.

Olli: ping me on IRC if I'm blocking on any issues

Patrick: there are also some outstanding things on my to-do list - particularly having a think about converting tiltX/tiltY to also provide the Apple-style orientation values ... at least as an initial note. PEP includes this, to my knowledge, so will see if i can grab something from there.

<scribe> ACTION: get outstanding extension sections added to the core spec by next call 13 November, in preparation for FPWD

<trackbot> Error finding 'get'. You can review and register nicknames at <https://www.w3.org/2012/pointerevents/track/users>.

<scribe> ACTION: contact PLH to check what the steps for FPWD are explicitly

<trackbot> Error finding 'contact'. You can review and register nicknames at <https://www.w3.org/2012/pointerevents/track/users>.

Summary of Action Items

[NEW] ACTION: contact PLH to check what the steps for FPWD are explicitly
[NEW] ACTION: get outstanding extension sections added to the core spec by next call 13 November, in preparation for FPWD
 

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/10/30 15:29:05 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: patrick_h_lauke NavidZ Olli_Pettay
No ScribeNick specified.  Guessing ScribeNick: patrick_h_lauke
Found Scribe: Patrick H. Lauke

WARNING: No "Topic:" lines found.

Agenda: https://lists.w3.org/Archives/Public/public-pointer-events/2019OctDec/0016.html

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: added contact extension get outstanding plh sections

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]