Improve clarity of render-blocking related terms #7870
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an editorial change. The original definition of "render-blocking" can be confusing because it's mostly reflecting the
blocking
attribute's value, and as a result, a render-blocking element may actually have never blocked rendering.This PR revises the terms so that:
(This is currently a draft PR. I'm also working on the Fetch spec to add render-blocking information to
Request
objects, which may depend on this PR)/dom.html ( diff )
/indices.html ( diff )
/links.html ( diff )
/scripting.html ( diff )
/semantics.html ( diff )
/urls-and-fetching.html ( diff )