Nav Timing

<yoav> https://github.com/w3c/navigation-timing/issues/65

two issues: merging specs --> we agreed on RT+NT; second is making sure links are correct and we have steps to prevent

<scribe> ACTION: yoav to open new issue on charter-webperf to audit links and determine if/what build infra (and processes) we can put in place to keep links good

<yoav> https://github.com/w3c/navigation-timing/issues/83

todd: filed because quick testing showed that we had some differences between UAs
... the case is: main doc has unload handler, and subdocs have unload handlers; the unload time of parent doc should include time of child unload?

<scribe> ACTION: Nick and Yoav to investigate what the expected behavior is, wire up some tests Nick + Yoav will investigate

<yoav> https://github.com/w3c/navigation-timing/issues/84

<scribe> ACTION: Yoav to compare processing vs attribute definitions and see if there are any changes to be made

Resource Timing

<yoav> https://github.com/w3c/resource-timing/issues/82

<yoav> https://github.com/w3c/resource-timing/issues/141

Todd: we need a test, so we can agree on what we're solving, and see what the differences are

<scribe> ACTION: Todd to wire up a WPT test

<yoav> https://github.com/w3c/resource-timing/issues/96

Yoav: related to above

AI: extend the WPT test to include logic for whether entry is dropped
... update the spec

<yoav> https://github.com/w3c/resource-timing/issues/139

AI: wire up the test to see what the current behavior is?

Page Visibility

<yoav> https://github.com/w3c/page-visibility/issues/34

<xiaoqian> https://github.com/w3c/page-visibility/pull/38

Todd: the language here needs to be "MAY", it is possible to implement on some platforms

<scribe> ACTION: Todd and xiaoqian to iterate on #38: https://github.com/w3c/page-visibility/pull/38/files

<yoav> https://github.com/w3c/page-visibility/issues/40

We got a ping from plh@ on this, @xiaoqian will draft an update

<yoav> https://github.com/w3c/page-visibility/issues/37

There is no process to update old L1, close with no action.

<scribe> ACTION: Yoav to followup on issue and resolve with no action.

Performance Timeline

<yoav> https://github.com/w3c/performance-timeline/issues/77

proposal: add a register hook in PerfTimeline, and have specs call into it to register new entryTypes

<scribe> ACTION: Ilya to (re)draft based on old commit

Todd: we believe that this is important feature to ship PerformanceObserver; it's a blocker feature.

NavPreload: Edge has it implemented in dev version

<yoav> https://github.com/w3c/performance-timeline/issues/81

Next Call

RESOLUTION: next design call, tentatively: July 26th, Aug 2nd

<scribe> ACTION: yoav and Ilya to review / update dashboard @ http://w3c.github.io/webperf-dashboard/