Contact emails nrosent...@chromium.org
Explainer None Specification https://w3c.github.io/resource-timing/#dom-performanceresourcetiming-finalresponseheadersstart Summary Resource timing: - responseStart returns the first response, either early hints (interim) or final - Expose the final response headers (2xx/4xx/5xx) time as finalResponseHeadersStart. Blink component Blink>PerformanceAPIs>ResourceTiming TAG review None TAG review status Not applicable Risks Interoperability and Compatibility This fixes responseStart to work like before and like firefox/safari, which makes it an interop *fix*. Compat-wise, this would change current dashboards that rely on the current chromium behavior of responseStart, and we would need to reach out to RUM providers who rely on these dashboards to update. Gecko: Positive (https://github.com/mozilla/standards-positions/issues/1108) Mozilla participated in the WebPerfWG meeting where we resolved on this. WebKit: No signal (https://github.com/WebKit/standards-positions/issues/424) Web developers: No signals 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 None Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)? Yes Is this feature fully tested by web-platform-tests? Yes https://wpt.fyi/results/resource-timing/interim-response-times.html?label=experimental&label=master&aligned https://wpt.fyi/results/resource-timing/interim-response-times.h2.html?label=experimental&label=master&aligned Flag name on about://flags ResourceTimingFinalResponseHeadersStart Finch feature name ResourceTimingFinalResponseHeadersStart Requires code in //chrome? False Tracking bug https://b.corp.google.com/issues/40251053 Availability expectation The change to responseStart is already available in the web platform mainline, and this aligns with it. Adoption expectation RUM providers rely on current behavior, so they would have to align very quickly by adopting the new values. Adoption plan DevRel outreach and using the existing RUM provider partner channels. Estimated milestones Shipping on desktop 133 DevTrial on desktop 132 Shipping on Android 133 DevTrial on Android 132 Shipping on WebView 133 Anticipated spec changes Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (eg links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (eg, changing to naming or structure of the API in a non-backward-compatible way). This is a resolution of https://github.com/w3c/resource-timing/issues/345 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5158830722514944?gate=5072033166393344 This intent message was generated by Chrome Platform Status. -- 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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6734969c.2b0a0220.3644d.03ac.GAE%40google.com.
