Contact emailsnrosent...@chromium.org Specificationhttps://github.com/w3c/resource-timing/pull/366
Summary Expose timings about final response headers start/end and response body time. Requested by people who use RT-based dashboards as a consequence of 103 Early hints. Blink componentBlink>PerformanceAPIs>ResourceTiming <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EPerformanceAPIs%3EResourceTiming> TAG reviewNone TAG review statusNot applicable Risks Interoperability and Compatibility This feature changes the meaning of responseStart. Since this change would affect only for the current users of early hints, which is a new feature in itself, the risk can be mitigated with communication. The handful of partners known to use early hints were already contacted. *Gecko*: Worth prototyping ( https://github.com/mozilla/standards-positions/issues/722) *WebKit*: No signal ( https://github.com/WebKit/standards-positions/issues/109) Safari has not implemented early hints yet, so it's not applicable yet. *Web developers*: Positive ( https://github.com/w3c/resource-timing/issues/345) Requested by multiple partners (Shopify, Wix) *Other signals*: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? None Debuggability Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?Yes Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ?Yes Flag nameResourceTimingInterimResponseTimes Requires code in //chrome?False Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1402089 Estimated milestones Shipping on desktop 115 Shipping on Android 115 Shipping on WebView 115 Anticipated spec changes Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way). None Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5086730938482688 Links to previous Intent discussions This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYZ%2BvwLUX0jfxZ8qsv0k8TzyZSR%3DgqfPwcYwSaKVDCBjaQ%40mail.gmail.com.