Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve clarity of render-blocking related terms #7870

Merged
merged 1 commit into from
May 3, 2022

Conversation

xiaochengh
Copy link
Contributor

@xiaochengh xiaochengh commented Apr 28, 2022

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:

  • "Potentially render-blocking" is used to reflect the attribute value
  • "Render-blocking" is used to indicate whether rendering is being blocked by the element

(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 )

@xiaochengh xiaochengh marked this pull request as ready for review May 2, 2022 22:05
@xiaochengh
Copy link
Contributor Author

@domenic

I found this PR necessary for doing further work on the Fetch PR. So PTAL, thanks!

@domenic domenic merged commit 5710d64 into whatwg:main May 3, 2022
@domenic domenic added clarification Standard could be clearer topic: rendering labels May 3, 2022
aarongable pushed a commit to chromium/chromium that referenced this pull request May 27, 2022
This this the implementation-side follow-up of the spec change:

whatwg/html#7870

Bug: 1271296
Change-Id: I77f91437c000301f7dcc0bb60f5b6f6011f7e48b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3669845
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1008322}
mjfroman pushed a commit to mjfroman/moz-libwebrtc-third-party that referenced this pull request Oct 14, 2022
This this the implementation-side follow-up of the spec change:

whatwg/html#7870

Bug: 1271296
Change-Id: I77f91437c000301f7dcc0bb60f5b6f6011f7e48b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3669845
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1008322}
NOKEYCHECK=True
GitOrigin-RevId: e53ee9d0e4f7357adb998bf9d270f7cb610081dc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Standard could be clearer topic: rendering
Development

Successfully merging this pull request may close these issues.

2 participants