Documenting renderBlockingStatus in Resource Timing

[abinpaul1]

Summary

New field renderBlockingStatus in PerfomanceResourceTiming to indicate the render-blocking nature of a resource. The attribute takes away the burden of having to rely on complex heurestics to determine which resources were actually render-blocking and provides a direct signal from the browser.

Explainer : https://github.com/abinpaul1/resource-timing/blob/render-blocking-status-explainer/Explainer/Render_Blocking_Status.md

Spec changes : w3c/resource-timing#327

Motivation

Adding documentation for new attributerenderBlockingStatus introduced to Resource Timing. Adding sample code to demonstrate usage of the attribute.

Supporting details

CR Bug : https://bugs.chromium.org/p/chromium/issues/detail?id=1337256
Chrome status entry : https://chromestatus.com/feature/5166965277589504

Related issues

Metadata

• Adds a new document
• Rewrites (or significantly expands) a document
• Fixes a typo, bug, or other error

[bsmth]

Hi @abinpaul1, thanks for opening the PR. I'm just checking if you're planning to pick this one up again or how you'd like to proceed. Thanks a lot :)

[abinpaul1]

I was thinking I'd have to wait for Chrome 107 to ship which would be the first browser release to have this enabled. I'm happy to continue working on this right away. Please feel free to start a review for this and I can adjust it based on feedback or I'm also open to handing it over if thats preferred.

[bsmth]

I'd have to wait for Chrome 107 to ship

Thanks a lot, I just had a look through the Chrome bug and it looks like it's expected to ship soon, is that right? Feel free to ping me to have another look! :)

[abinpaul1]

Yes, stable is expected to ship towards end of October. I am going ahead and marking the PR as ready for review.

[bsmth]

OK thanks a lot. There will be some downtime from the team during the next week or so; we will get to this afterwards. I'm happy to pick it up then.

[abinpaul1]

@bsmth I'm not able to get around an error when I add this new document for renderBlockingStatus. I am trying to keep it similar to how all the other fields in Resource Timing are added, but I get this error.

MacroBrokenLinkError from domxref [line 112:7] 
Explanation: /en-US/docs/Web/API/PerformanceResourceTiming/renderBlockingStatus does not exist `

Mainly the document isnt being picked up for some reason. Navigating to /en-US/docs/Web/API/PerformanceResourceTiming/renderBlockingStatus gives page not found
I feel I'm misssing something to get the links to work correctly

[bsmth]

I feel I'm misssing something to get the links to work correctly

It could be a case-sensitivity thing on the parent directory for the document. I can take a look shortly

[github-actions]

Preview URLs

• /en-US/docs/Web/API/PerformanceResourceTiming/renderBlockingStatus
• /en-US/docs/Web/API/PerformanceResourceTiming

(this comment was updated 2022-11-02 10:44:00.349468)

[bsmth]

@abinpaul1 this is fixed now in ac79f03, the parent dir is case-sensitive

[abinpaul1]

Cool! Thanks

[bsmth]

I tested in Chrome 108.0.5355.0 and works as expected. This should be on-hold until 107 stable release, but I think we can publish it then. We will need corresponding browser compat data for this first.

[abinpaul1]

I've opened a PR for adding the compat data : mdn/browser-compat-data#18046

[bsmth]

I've opened a PR for adding the compat data : mdn/browser-compat-data#18046

oh nice, you beat me to it 🙌🏻

[abinpaul1]

Hey @bsmth, Are we good to merge this?

[bsmth]

Hi @abinpaul1, I think the corresponding BCD PR has to be merged first. Once that's landed I think we're ready to go here.

[bsmth]

• Include render-blocking status browser compat data browser-compat-data#18046

BCD for this is merged, this PR can be merged when this is deployed (likely today).

[Josh-Cena]

This should be mergeable now?

[bsmth]

Thanks @abinpaul1, going to merge shortly