See also: IRC log
* keep Preload, Resource Hints, and rIC as part of the webperf group
* move Server Timing, Frame Timing, and Reporting + NEL to WICG
--> https://w3c.github.io/charter-webperf/ draft charter
Ilya: we have some implementations for the first set, and none for the second, thus the proposal
Yoav: makes sense to me
... Frame Timing is a bit more advance
Ilya: yes and no, but we keep changing subtantially and no update on the implementation side. could be convinced either way
Todd: we should ensure that we publish current work as Notes before we drop from the charter
... we could also allow folks from the WICG to contribute
Yoav: only thing is that the work on server timing wouldn't move forward
Ilya: so, transfer ownership of the repo of WICG and publish as Notes, and then readopt them in the future if needed
plh: ok, so server timing, reporting, NEL. what about frame timing?
todd: don't foresee us implementing unless there is incredible adoption
ilya: ok, then I think we'll keep working on the use cases and current design isn't the best
... so it's reasonable to move to WICG
<scribe> ACTION: plh to publish Frame Timing, Server Timing, Reporting, NEL [recorded in http://www.w3.org/2016/05/04-webperf-irc]
<trackbot> Created ACTION-169 - Publish frame timing, server timing, reporting, nel [on Philippe Le Hégaret - due 2016-05-11].
Ilya: we added some estimates as well
igrigorik: Make sure to address L1 comments: https://lists.w3.org/Archives/Public/public-web-perf/2016Apr/0009.html
<scribe> ACTION: plh to make sure the draft is up-to-date [recorded in http://www.w3.org/2016/05/04-webperf-irc]
<trackbot> Created ACTION-170 - Make the draft is up-to-date [on Philippe Le Hégaret - due 2016-05-11].
plh: will keep cranking the wheel on that one
Yoav: I'd like to use resource timing to test the preload implementation
... implementation is flaky at the moment
... if I get to a stable implementation, I might try to have it ship in webkit
Ilya: for L2, the issues around resources that don't return responses, I summarized the status on the chrome bug and started a thread with security and privacy team at Google
Ilya: got some good feedback
... should we publish as a Note
Todd: we should
... only downside is that we'll get feedback :)
Ilya: we're having those discussions anyway
RESOLUTION: let's publish those best practices as a Note
<scribe> ACTION: plh to create a repo for best practices document [recorded in http://www.w3.org/2016/05/04-webperf-irc]
<trackbot> Created ACTION-171 - Create a repo for best practices document [on Philippe Le Hégaret - due 2016-05-11].
Ilya: I'll transform into respec
Ilya: having a change section would be good
plh: I'll make a PR for that
... and keep into iterating on the tests
<igrigorik> riC test: https://github.com/w3c/web-platform-tests/pull/2163
Ilya: we may have to add some additional tests
plh: i'll add that to my TODO list
Ilya: I need to add a privacy section
... we kind of have one but need to pull it out
Todd: I touched based with Justin on that front
... one concern is that Chrome pipeline becoming the pipeline for developers
... the spec is overly specific sometimes. I need to check on that.
Ilya: concept of idle time is user agent defiend
Todd: main problem comes from layout
... so ordering of events and when layout happens
... trick is that guidance shouldn't be to a specific engine
... so I need to figure this out
... will look over it next week or two
<igrigorik> html updates: https://github.com/whatwg/html/pull/1141
Yoav: Domenic is doing some cleanups related to HTML
... and adding the link relations to HTML itself
... and ask if the relations apply only to link or also a and area
... I see a weak use cases for a and area
... I don't think they're implemented anywhere else, except for prefetch
Ilya: context is that prefetch was supported for a and area and domenic was asking for others
... I don't see a huge value so I'm ok to remove those
... but not even sure on prefetch for a and area
Yoav: ok, so next step is testing to see who supports what
Todd: don't know for Edge
Ilya: we can write a quick test and see what happens
... I found that prerender has some issues in Edge for example
... in all scenarios
... it's tricky to get some tests since we get no clear signals
... looking at TCP dumps to verify that it's working
Todd: e.g. dns-prefetch
plh: would be good to send feedback to WebDriver folks btw
Ilya: L1 defines its own time origin because we didn't have the current def
... we're duplicating for historical reasons
plh: maybe change the styling of that section?
Ilya: or remove it and link to L1
<igrigorik> sorry guys, need to drop off, dialing back in..
"All time values defined in this appendix are measured in milliseconds since midnight of January 1, 1970 (UTC)."
plh: I'll invite them for a presentation.
Next call is in 2 weeks.