Intent to Ship: Render-blocking status in Resource Timing
Abin Paul
Contact emails
Explainer
Specification
https://github.com/w3c/resource-timing/pull/327
Design docs
Summary
Adds a field to PerformanceResourceTiming to indicate the render-blocking status of a resource. Currently from a developer perspective, the only way to determine which resources were actually render-blocking is to rely on complex heuristics. The new field would instead provide a direct signal regarding the same.
Blink component
Blink>PerformanceAPIs>ResourceTiming
TAG review
https://github.com/w3ctag/design-reviews/issues/753
TAG review status
Issues addressed
Risks
Interoperability and Compatibility
Gecko: Positive (https://github.com/mozilla/standards-positions/issues/662#issuecomment-1171568555)
WebKit: No signal (https://github.com/WebKit/standards-positions/issues/17)
Web developers:
Positive reception towards a very similar feature for lab testing. https://blog.webpagetest.org/posts/new-render-blocking-indicator-in-chrome-and-webpagetest/
https://twitter.com/tkadlec/status/1417543014705246214
Other signals:
Ergonomics
No
Activation
No risks
Security
No risks
WebView application risks
Does this intent deprecate or change behaviour of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
Debuggability
The new attribute shows up in Devtools. No implementation changes are required.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes
Adds new attribute to PerformanceResourceTiming, so available on all platforms that support the same
Is this feature fully tested by web-platform-tests?
Yes
DevTrial instructions
Flag name
chrome://flags/#enable-experimental-web-platform-features
Requires code in //chrome?
False
Tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=1337256
Non-OSS dependencies
Does the feature depend on any code or APIs outside the Chromium open source repository and its open-source dependencies to function?
No
Sample links
Estimated milestones
Chrome for desktop 107
Chrome for Android 107
Android Webview 107
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).
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5166965277589504
Links to previous Intent discussions
Intent to prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM2ZH3dimwFkdjtC_1O5imD9HNJ6QvNPPuPJ5Me9ushAT9CKiA%40mail.gmail.com
This intent message was generated by Chrome Platform Status.
slightlyoff via Chromestatus
Daniel Bratell
LGTM2
/Daniel
Such a great addition! LGTM1--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/000000000000feb36605e5eadd3a%40google.com.
Chris Harrelson
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/eba13fa4-db6f-c590-9a7c-4e7e93398eaf%40gmail.com.