- From: Xiaoqian Wu <xiaoqian@w3.org>
- Date: Fri, 15 Dec 2017 23:21:46 +0800
- To: Public-web Perf <public-web-perf@w3.org>
Hi, The minutes from the 11 Dec 2017 Beihang Site Meeting are available: https://www.w3.org/2017/12/14-webperf-minutes.html also as plain text below: -------------------- WebPerf WG "Spec to Rec" Call 14 Dec 2017 Agenda Attendees Present Dale, Charles, igrigorik, Yoav, Nic, Nolan, Philip, Tim, Todd, xiaoqian Regrets Chair Todd, igrigorik Scribe igrigorik Contents Topics HR-time Issues Resource Timing User Timing Navigation Timing next call Summary of Action Items Summary of Resolutions <scribe> scribe: igrigorik HR-time Issues todd: one issue remaining on HR-time dale: PR is in place, should be good ... tests are in pretty good shape, but would like to get more eyes on it ... fails in FF today, potentially due to implementation bug ... added some details in the test PR ... safari is not testable today because it's a lot more aggressive about how popups are handled ... don't if/how to proceed there spec update https://github.com/w3c/hr-time/pull/54 tests https://github.com/w3c/web-platform-tests/pull/8488 RESOLUTION: spec text is good, merged. [tests: waiting for Boris to comment on Dale's repro case] todd: we have two passing implementations, good to publish ; let's wait for Boris to followup. Resource Timing Nick: auditing v3 branch vs v2 differences ... also going through open v2 issues Issue #120 https://github.com/w3c/resource-timing/issues/120 scribe: discussed at TPAC, one of the followups was to gather some RUM data ... we gathered bulk data for couple customers ... we did find some instances of timestamps in non-standard order ... most of those had requestStart < connectEnd ... plus some weird data, e.g. requestStart having a value but others being zero ... not sure if its browser bugs or bugs in our collection ... near 70% of weird ordering is for QUIC todd: Edge has attempted to ship TFO in multiple release, so far we've had to back off each time ... don't have enough backoff to detect edge cases ... still WIP and aiming to make it live ... could next step here be to summarize per UA and see if we can isolate some repro cases? Nic: my suggestion is that some timestamps should have hard ordering, but in others we may want to allow some flexibility <scribe> ACTION: Nic to followup on issue with next step Issue #130 https://github.com/w3c/resource-timing/issues/130 Nic: looking into how RT works with media use cases ... documented in the issue differences between browsers today ... e.g. video can trigger poster image ... how should it be reported? spec suggests "video", which makes sense.. but it's not obvious that image is being downloaded. ... also, what about <source>: today it shows up as other, video or blank todd: let's label each of these use cases and clarify the behavior in current L2 spec ... for this case, it sounds like we need to file some implementation bugs and clarify the spec Nic: I'll followup on the issue. Issue #122 https://github.com/w3c/resource-timing/issues/122 Todd: we can add a normative MAY for 0.9; we don't need to fight the battle to register it with IETF User Timing Tim: looked into usage of UT timestamps in the wild ... found that NT1 timestamps are used enough that we can't deprecate them outright ... we'll have to support that in L2 Philip: for L3, we didn't see any usage of objects so we should be in good shape there ... in NT2, using NT1 timestamps has different time origin Todd: right, we need to map these to NT2 concepts ... in the spec, and define that clearly in the spec Philip: what about Worker case? ig: in worker we don't expose NT Todd: we should probably just throw, NT in worker doesn't make sense Navigation Timing Issue #79 https://github.com/w3c/navigation-timing/issues/79 Todd: Andy is calling out that beforeUnload execution Ilya: I don't believe we can expose this due to privacy AI: Ilya to followup on the thread, suggesting WONTFIX next call RESOLUTION: next call will be on Jan 5th Summary of Action Items [NEW] ACTION: Nic to followup on issue with next step Summary of Resolutions spec text is good, merged. next call will be on Jan 5th [End of minutes] -------------------- Thanks. -xiaoqian On 2017-12-13 07:51, Todd Reifsteck wrote: > Ilya and I have discussed how we can ensure that we see forward > progress on specs that are past our goal dates. As an attempt to > improve our issue throughput, we are moving to a structure of > alternating call focus. The 12/14 call's focus will be on past-due > specs and the issues that are blocking them. > > Please let us know ASAP if this time does not work for any > editors/blocking issue owners. > > Thanks! > Todd & Ilya > > CALL DETAILS: > > Hangout: > https://hangouts.google.com/hangouts/_/chromium.org/webperf-wg [1] > > Tentative agenda: > > https://docs.google.com/document/d/10dz_7QM5XCNsGeI63R864lF9gFqlqQD37B4q8Q46LMM/edit#heading=h.38orgzczc6zb > [2] > > If you have other topics you'd like to discuss, please feel free to > add to the doc above. > > > > Links: > ------ > [1] https://hangouts.google.com/hangouts/_/chromium.org/webperf-wg > [2] > https://docs.google.com/document/d/10dz_7QM5XCNsGeI63R864lF9gFqlqQD37B4q8Q46LMM/edit#heading=h.38orgzczc6zb
Received on Friday, 15 December 2017 15:21:48 UTC