navigation-timing
navigation-timing copied to clipboard
Navigation Timing
This addresses a few issues around `workerStart` especially in the case of redirects: * `workerStart` needed to be added to the diagram https://github.com/w3c/navigation-timing/issues/128 (see screenshot below) * I've added a...
## Important info - URL to affected spec:https://w3c.github.io/navigation-timing/#dom-performancetiming-redirectend - ReSpec version: 26.8.12 - [x] I did a "hard refresh", but it's still busted. ## Description of problem **What happened?** The...
In TPAC 2021, we had a positive feedback on reporting back/forward cache NotRestoredReasons extending Navigation Timing API. e.g. Exposing why a page is not restored from back/forward cache in Navigation...
One of the challenges we've had at Microsoft is measuring the performance impact of a cold start launch for a particular site. This particularly apparent in PWA scenarios where the...
We're working on navigational prefetch and think it would be useful for developers to, at a minimum, be able to tell whether the page was prefetched (so they can look...
Chromium recently [got a report](https://bugs.chromium.org/p/chromium/issues/detail?id=1317666) that it's hard for folks deploying [Critical-CH](https://github.com/WICG/client-hints-infrastructure/blob/main/reliability.md#critical-ch) as a backup mechanism to [ACCEPT_CH](https://github.com/WICG/client-hints-infrastructure/blob/main/reliability.md#accept_ch) frames to know if/when that backup was actually used, and triggered a...
In order to produce accurate BFCache hit-rate stats a page must be able to tell whether a navigation was even eligible for BFCache in the first place. Currently there is...
The specifications for [Navigation Timing API 2](https://www.w3.org/TR/navigation-timing-2/) or [Resource Timing API 2](https://www.w3.org/TR/resource-timing-2/) does not make it explicitly clear what is the definition or the expected value to be observed for...
From the documentation of Performance.measure(), it seems like the startMark and endMark still depend on PerformanceTiming, which is clearly being depreciated. Is there a way to have it now default...
When we have a navigation with cross-origin redirects, we're hiding `redirectStart` and `redirectEnd` from the final document. However, because the `timeOrigin` for all the navigation timing entries is the navigation...