Resource Timing PR : https://github.com/w3c/resource-timing/pull/327
Fetch PR : https://github.com/whatwg/fetch/pull/1449
Adds a field to PerfomanceResourceTiming 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.
Currently in order to determine which resources were actually render blocking and which ones were not, developers have to rely on heuristics.
By providing a web exposed field, developers can get a direct signal from the browser regarding the render blocking nature of each resource.
Gecko: No signal
WebKit: No signal
Reception towards a similar feature introduced in Chromium was very positive. The article and tweet linked below is a good indicator.
Does this intent deprecate or change behaviour of existing APIs, such that it has potentially high risk for Android WebView-based applications?
No milestones specified
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM2ZH3dimwFkdjtC_1O5imD9HNJ6QvNPPuPJ5Me9ushAT9CKiA%40mail.gmail.com.