Report render blocking status for <link> and <script>

[abinpaul1]

These changes are to support addition of a render blocking status field to Perfomance resource timing. Further details are available at w3c/resource-timing#327

Fetch side changes: whatwg/fetch#1449

• At least two implementers are interested (and none opposed):
  • …
  • …
• Tests are written and can be reviewed and commented upon at:
  • …
• Implementation bugs are filed:
  • Chrome: …
  • Firefox: …
  • Safari: …
  • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): …
  • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): …

(See WHATWG Working Mode: Changes for more details.)

---

/links.html ( diff )
/semantics.html ( diff )
/webappapis.html ( diff )

[abinpaul1]

These changes are not needed as we are reusing Request's render-blocking boolean in fetch spec to get the render-blocking status