W3C home > Mailing lists > Public > public-web-perf@w3.org > March 2019

Re: WebPerfWG triage call - Friday March 8th @ 11am PST

From: Yoav Weiss <yoav@yoav.ws>
Date: Fri, 8 Mar 2019 21:34:55 +0100
Message-ID: <CACj=BEheD-uxtw7d0-JQNrDr-H9CWObkv6Hd8SuG5tOPajAcqg@mail.gmail.com>
To: public-web-perf <public-web-perf@w3.org>
Thanks all for attending! :)

Minutes from the call can now be found here
<https://docs.google.com/document/d/e/2PACX-1vRdTGJrBs-8u6SqDBeOSSpSIglWXcwBNpTs10adg7KnmIpwRuZ8Yjob5IGxYwrACPQoKFvEq1brJo12/pub>.
Copying them to the list for safe keeping:

WebPerfWG March 8th 2019 - Triage call
Admin

Next design call: Wednesday 14th, 11AM PST

User Timing L3

FPWD L3 published: https://w3c.github.io/user-timing/
<https://www.google.com/url?q=https://w3c.github.io/user-timing/&sa=D&ust=1552080783848000>

Nicolas: on last call we resolved to do a poll to confirm measure API design

Yoav: the twitter poll is showing 70% for measure vs measureWithOptions

… given that the group was leaning this direction as well, the proposal is
to override measure()

… what is the implementation status?

Nicolas: OK, resolved: we’ll use measure().

Nicolas: other then measure() we have everything wired up, behind the flag

Todd: what’s the plan for shipping this?

Nicolas: L3 FPWD is published, I don’t believe any of the outstanding
issues are blocking for us (Chrome) to ship L3 or would cause issues down
the road

AI: Nicolas to update and resolve measure issue

AI: Nicolas to review other open (10) issues
Resource Timing

Status
<https://www.google.com/url?q=https://github.com/w3c/resource-timing/issues/71%23issuecomment-462167655&sa=D&ust=1552080783851000>
of
RT L2 tests

   - Pending WPTs


   - Add nested-context resource-timing tests
   <https://www.google.com/url?q=https://github.com/web-platform-tests/wpt/pull/13823&sa=D&ust=1552080783852000>
   - Test XO redirection sandwich with and without TAO
   <https://www.google.com/url?q=https://github.com/web-platform-tests/wpt/pull/13518&sa=D&ust=1552080783852000>
   - Test TAO origin check on different ports
   <https://www.google.com/url?q=https://github.com/web-platform-tests/wpt/pull/13508&sa=D&ust=1552080783853000>
   - Tao null opaque origin test
   <https://www.google.com/url?q=https://github.com/web-platform-tests/wpt/pull/13507&sa=D&ust=1552080783853000>

Yoav: there are some issues with our WPTs

… we still have 7 different tests that are passing in only one
implementation

… it also seems like it’s the same underlying issues for some (~3) of them

… can we get folks on Firefox / Safari side to get 2 passing implementations

Todd: the goal here is to either have a bug with intent to fix, or explicit
feedback objecting

… that would be sufficient for us

Markus: we have a new person on FF side looking into these failures

… I hope we’ll have feedback soon

Yoav: fyi, we’re hitting flakiness bugs on WPT bots for FF nightly

… Ryosuke, could we file issues for the non-passing tests?

Ryosuke: unfortunately we don’t have anyone looking at these

… these are not high-priority compat issues, at least to our knowledge

Todd: let’s make sure that FF engineers review and agree on the proposed
behaviors

… this will unblock us from shipping L2 CR

Yoav: FYI, I’ve also found some edge cases in the spec that I’ve added
tests for, which may add some new failures; working on landing them, some
are pending review from Firefox side; most of these tests are requests from
Anne

Markus: ty for wiring up those test from our feedback!
NavigationTiming

   - 6 issues
   <https://www.google.com/url?q=https://github.com/w3c/navigation-timing/issues?q%3Dis%253Aissue%2Bis%253Aopen%2Blabel%253Adiscuss&sa=D&ust=1552080783856000>
to
   discuss
   - PR
   <https://www.google.com/url?q=https://github.com/w3c/navigation-timing/pull/103&sa=D&ust=1552080783857000>
    and WPT
   <https://www.google.com/url?q=https://github.com/web-platform-tests/wpt/pull/15746&sa=D&ust=1552080783857000>
to
   close #95
   <https://www.google.com/url?q=https://github.com/w3c/navigation-timing/issues/95&sa=D&ust=1552080783858000>


Unload event TAO check should be for all redirects
<https://www.google.com/url?q=https://github.com/w3c/navigation-timing/issues/95&sa=D&ust=1552080783858000>
 #95

Yoav: correct wording should be that only if all redirects pass TAO that
this should be exposed

… we agreed on this on last call and I wrote a spec update + tests for it,
need folks to review

… https://github.com/w3c/navigation-timing/pull/103
<https://www.google.com/url?q=https://github.com/w3c/navigation-timing/pull/103&sa=D&ust=1552080783859000>
-
ptal

supported entry types needs to be context aware
<https://www.google.com/url?q=https://github.com/w3c/navigation-timing/issues/102&sa=D&ust=1552080783860000>
 #102

Charles: the navigation entry type should not be exposed for Workers

Yoav: this doesn’t seem contentions

Nicolas: we fixed this in Chrome, agree that we should update the spec

Yoav: this may not be a NT specific issues?

Nicolas: right, for example worker may not expose longtasks, etc..

… probably a performance timeline issue, that might require an update in NT

Yoav: is this an L2 blocker?

Charles/Nicolas: no

Yoav: marking as L3

Todd: as written the spec would lead you to expect that it should be
exposed in Worker

Nicolas: I think we can update the NT spec with a monkey patch, it’s a
minor issue that shouldn’t block L2

Yoav: OK, I’ll change it back to L2 and will note that this should not
block on Perf Timeline

workerStart should be clearly defined as applicable to the last SW
<https://www.google.com/url?q=https://github.com/w3c/navigation-timing/issues/100&sa=D&ust=1552080783862000>
 #100

Yoav: in a navigation it’s possible for multiple SW to be involved

… we should clarify that the time reflects the last one

… we can define it in a handwavy way today, and then rebase against Fetch
for L3

… proposal to mark it as L2 and do as described

[no objections]

workerStart should be gated on timing-allow check
<https://www.google.com/url?q=https://github.com/w3c/navigation-timing/issues/99&sa=D&ust=1552080783863000>
 #99

Yoav: definitely an L2 blocker

Should navigationEntry's navigationType be updated according to the parent
page?
<https://www.google.com/url?q=https://github.com/w3c/navigation-timing/issues/85&sa=D&ust=1552080783863000>
 #85

Yoav: definitions for this exist in Fetch and HTML

… but I don’t think we can define better processing until we do Fetch
integration

… I think this something we can/should do in L3

Todd: agreed, we need to create more tests, etc.

[resolved, mark L3]

should unloaded iframes be included in their parent document's unload
duration?
<https://www.google.com/url?q=https://github.com/w3c/navigation-timing/issues/83&sa=D&ust=1552080783864000>
 #83

Yoav: we discussed this ~year ago, don’t think we’ve made progress

… we need to write the tests to see if there is existing agreement on the
behavior

Todd: agree, this is a less significant issue than previous issue

… if we’re move previous issue to L3 then same here

Yoav: sgtm

[resolved, marking L3]

https://wpt.fyi/results/navigation-timing?label=master&product=chrome%5Bexperimental%5D&product=edge&product=firefox%5Bexperimental%5D&product=safari%5Bexperimental%5D&aligned&q=navigation-timing
<https://www.google.com/url?q=https://wpt.fyi/results/navigation-timing?label%3Dmaster%26product%3Dchrome%255Bexperimental%255D%26product%3Dedge%26product%3Dfirefox%255Bexperimental%255D%26product%3Dsafari%255Bexperimental%255D%26aligned%26q%3Dnavigation-timing&sa=D&ust=1552080783866000>

Yoav: Safari has a lot of red, guessing due to lack of PerformanceObserver

Markus: we’re looking into these as well.

AI: Yoav and Charles will triage outstanding L2 issues
<https://www.google.com/url?q=https://github.com/w3c/navigation-timing/milestone/1&sa=D&ust=1552080783867000>

PerformanceTimeline L2 republishing

https://github.com/w3c/performance-timeline/milestone/2
<https://www.google.com/url?q=https://github.com/w3c/performance-timeline/milestone/2&sa=D&ust=1552080783868000>


   - Ensure
   <https://www.google.com/url?q=https://github.com/w3c/performance-timeline/issues/100&sa=D&ust=1552080783868000>
tests
   are clean
   - Buffered flag
   <https://www.google.com/url?q=https://github.com/w3c/performance-timeline/issues/81&sa=D&ust=1552080783869000>
    removal

Nicolas: I believe above are the only two outstanding issues. Looking at
WPT.fyi..

https://wpt.fyi/results/performance-timeline?label=master&product=chrome%5Bexperimental%5D&product=edge&product=firefox%5Bexperimental%5D&product=safari%5Bexperimental%5D&aligned&q=performance-timeline
<https://www.google.com/url?q=https://wpt.fyi/results/performance-timeline?label%3Dmaster%26product%3Dchrome%255Bexperimental%255D%26product%3Dedge%26product%3Dfirefox%255Bexperimental%255D%26product%3Dsafari%255Bexperimental%255D%26aligned%26q%3Dperformance-timeline&sa=D&ust=1552080783870000>

Charles: failing po-observe tests should go away due to removal of buffered
flag?

Nicolas: there may be other failures there

… how do we republish?

Yoav: create an L2 branch off the current gh-pages

… revert or force push to point that we want

Nicolas: which point do we want to point to?

Yoav: can we just manually remove it?

Todd: we want to keep supported entryTypes

... just remove the buffered flag.

Nicolas: ok, that works

… fyi, some tests will be failing to align with the new entryTypes

Todd: yep, as long as you can note which tests need attention

Yoav: I’ll open an issue for “transition to CR”, where we can note tests,
etc.



On Thu, Mar 7, 2019 at 9:33 AM Yoav Weiss <yoav@yoav.ws> wrote:

> Hey all,
>
> Let's triage some issues! As we discussed on the last call, our triage
> call this week will be on Friday, rather than the usual Thursday.
>
> On the agenda
> <https://docs.google.com/document/d/10dz_7QM5XCNsGeI63R864lF9gFqlqQD37B4q8Q46LMM/edit?pli=1#heading=h.429ne9tny5ej>
> so far:
>
>    -
>
>    Status of UT L3 in Chrome?
>    -
>
>    Resource Timing
>    -
>
>       Status
>       <https://github.com/w3c/resource-timing/issues/71#issuecomment-462167655>
>       of RT L2 tests
>       -
>
>       Pending WPTs
>       -
>
>          Add nested-context resource-timing tests
>          <https://github.com/web-platform-tests/wpt/pull/13823>
>          -
>
>          Test XO redirection sandwich with and without TAO
>          <https://github.com/web-platform-tests/wpt/pull/13518>
>          -
>
>          Test TAO origin check on different ports
>          <https://github.com/web-platform-tests/wpt/pull/13508>
>          -
>
>          Tao null opaque origin test
>          <https://github.com/web-platform-tests/wpt/pull/13507>
>          -
>
>    NavigationTiming
>    -
>
>       6 issues
>       <https://github.com/w3c/navigation-timing/issues?q=is%3Aissue+is%3Aopen+label%3Adiscuss>
>       to discuss
>
>
> Please join us <https://meet.google.com/nog-ttdz-myg?hs=122>!
>
> Cheers :)
> Yoav
>
>
>
Received on Friday, 8 March 2019 20:35:38 UTC

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2019 20:35:39 UTC