W3C

- DRAFT -

PEWG

27 Nov 2019

Agenda

Attendees

Present
patrick_h_lauke
Regrets
Chair
Patrick H. Lauke
Scribe
Patrick H. Lauke

Contents


<scribe> Scribe: Patrick H. Lauke

Olli: do you have a link to latest CCSOM View

Patrick: https://drafts.csswg.org/cssom-view/

PLH: if you want me to, i can look at the ReSpec problem

Patrick: that'd be great, thanks

PLH: I will also set up automatic publishing once we hit FPWD

Patrick: do we need to change prose in spec to say "First Public Working Draft"?

<plh> https://w3c.github.io/pointerevents/

<plh> https://w3c.github.io/pointerevents/?specStatus=FPWD

PLH: no, but you can also pass parameters for magic to happen

<plh> https://w3c.github.io/pointerevents/?specStatus=FPWD;publishDate=2019-12-06

PLH: you can override configuration of ReSpec with parameters in the URL

Patrick: link for request to FPWD https://github.com/w3c/transitions/issues/new/choose

so information we need (see https://github.com/w3c/transitions/issues/new?assignees=plehegar&labels=Awaiting+Director%2C+Entering+FPWD&template=fpwd.md&title=FPWD+Request+for+%3Ctitle%3E)

so for "Is it a delta specification intended to become a W3C Recommendation?" is it yes?

PLH: NO, it's not just a delta, level 3 supersedes level 2
... we should mention that in the status

do it in the editor's draft already

Patrick: for " Information about implementations known to the Working Group" i think we only have Chrome at this point (for the new level 3 things)

PLH: do we have tests? if so, link to w3ptest (sp?) for it

Patrick: Navid will know

Link to the CfC https://github.com/w3c/pointerevents/issues/312

PLH: hoping to get Apple to implement

Patrick: they have it in Safari 13 but still listed as in development on https://webkit.org/status/#specification-pointer-events-level-2
... not sure after Level 3 there will be much more steam for new APIs/functionalities

but we'll see once we get there

PLH: if it comes to it, we'll put in maintenance mode

Patrick: [talks a bit about touch events as a spec that would be nice to update the CG note to touch events level 2]

<plh> /TR/pointerevents will keep pointing at Level 2 until Level 3 gets to CR

Patrick: agree

<plh> I'll update Level 2 to point to Level 3 in a note

Patrick: I will get in touch with Navid about the implementation status/tests info

if CfC passes, I will then file the FPWD request end of 5th/morning of the 6th

PLH: and I can have it done by following Tuesday (and will ensure automatic publication from that point on is set up)

Summary of Action Items

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/11/27 16:35:19 $

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

WARNING: Fewer than 3 people found for Present list!

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/0039.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: 

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]