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

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)

Succeeded: s/(?)/predicted points/

WARNING: No "Present: ... " found!
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy
        <amy> Present+

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