<scribe> Scribe: Patrick H. Lauke

<NavidZ_> Has the meeting started?

<NavidZ_> We are trying to connect but it tells us the meeting hasn't started yet

hmm

worked for me

https://mit.webex.com/mit/j.php?MTID=m9b2829b9c9ef2c228a3fad0a30137189

(using the computer audio. are you using the dial-in?)

question about what happens after v2. whether we want to recharter to work on v3.

desire from Google side to formalize into spec the extension work (new touch-action values for instance).

patrick to speak with philippe and send email to mailing list to ask about rechartering/continued work as WG rather than converting to community group

other aspects good to spec: how PEs align with RAF

https://github.com/w3c/pointerevents/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+-label%3Afuture-v3+

#167 https://github.com/w3c/pointerevents/issues/167

test will be added/updated by end of week ideally

<NavidZ_> https://github.com/w3c/pointerevents/issues/107

#107 https://github.com/w3c/pointerevents/issues/107

couldn't get automation script to send fractional coordinates. ella tried different approach, so will try that approach

#173 https://github.com/w3c/pointerevents/issues/173

both patrick and olli hadn't had a chance to look at this yet

navid: should have a test for this somewhere already, see if we need to align spec text with it
... what both edge and chrome do is fire boundary events on next interaction (?)

mustaq: we should fire after pointerup, instead of waiting for next event

https://w3c.github.io/spec-releases/milestones/?rec=2018-07-17&noFPWD=true

we should get the last substantive issue (173) resolved for 24th april

and get test results looking polished for then as well

not all tests need to pass, but need to show that the failing ones are being worked on / engines show a desire to move towards implementing

navid: next week is BlinkOn, so can't do call

patrick: we can deal with the last outstanding issues by email/GH comments
... I will check with PLH about the next stage (transition to CR) and the bureaucracy around recharter of the group

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
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 Navid Zolghadr Ella Ge Mustaq Ahmed
No ScribeNick specified.  Guessing ScribeNick: patrick_h_lauke
Found Scribe: Patrick H. Lauke

WARNING: No "Topic:" lines found.


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: 

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.)