Description
こんにちは TAG-さん!
I'm requesting a TAG review of Document Render-Blocking.
The Web is designed with a model for incremental rendering. When a Document is loading, the browser can render its intermediate states before fetching all the requisite sub-resources, executing all script or fetching/parsing the complete Document. While this is great to reduce the time for first paint, there is a tradeoff between showing a jarring flash of intermediate Document state (which could be unstyled or have more CLS) vs blocking rendering on high priority sub-resources within a reasonable timeout.
The render-blocking concept helps browsers in making this tradeoff. It lets authors specify the set of stylesheets and script elements which should block rendering. For example, a stylesheet with the rules necessary to ensure a stable layout. But authors can’t specify which nodes should be added to the DOM before first render. This proposal aims to fill this gap.
- Explainer¹ (minimally containing user needs and example code): https://github.com/WICG/view-transitions/blob/main/document-render-blocking.md
- User research: N/A
- Security and Privacy self-review²: https://github.com/WICG/view-transitions/blob/main/security-privacy-questionnaire-document-render-blocking.md
- GitHub repo (if you prefer feedback filed there): [View Transitions] Extend render-blocking to support Document whatwg/html#9332
- Primary contacts (and their relationship to the specification):
- Khushal Sagar (@khushalsagar), Google
- Noam Rosenthal (@noamr), Google
- Vladimir Levin (@vmpstr), Google
- Organization/project driving the design: Google
- External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5113053598711808
Further details:
- I have reviewed the TAG's Web Platform Design Principles
- The group where the incubation/design work on this is being done (or is intended to be done in the future): HTML
- The group where standardization of this work is intended to be done ("unknown" if not known): HTML
- Existing major pieces of multi-stakeholder review or discussion of this design: N/A
- Major unresolved issues with or opposition to this design: N/A
- This work is being funded by: N/A
You should also know that...
This feature is needed for cross-browser compliant implementation of cross-document View Transitions, reviewed at #851.
We'd prefer the TAG provide feedback as (please delete all but the desired option):
💬 leave review feedback as a comment in this issue and @-notify @khushalsagar @noamr.