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

[renderblocking] Allow manual unblocking of rendering #33774

Merged
merged 1 commit into from Apr 25, 2022

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Apr 25, 2022

This patch makes sure that we can manually unblock rendering on an
element by removing its blocking=render attribute or by simply
removing the element from DOM.

The only new implementation change is that when the blocking
attribute of a <style> or <script> element changes, if it changes to
non-render-blocking, then we unblock rendering. All other DOM changes
are already handled by existing code.

This patch also adds new WPT tests for the behavior.

Note: The spec does not require such behavior -- it only requires when
the UA must not render, but there's no requirement of when the UA must
render. So the tests are marked as "optional".

Bug: 1271296
Change-Id: Iead14b73014370ea72e6eeb6714b75cc56de974f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3601726
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#995853}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-3601726 branch 2 times, most recently from e322a38 to bbadfb2 Compare April 25, 2022 23:10
This patch makes sure that we can manually unblock rendering on an
element by removing its `blocking=render` attribute or by simply
removing the element from DOM.

The only new implementation change is that when the `blocking`
attribute of a <style> or <script> element changes, if it changes to
non-render-blocking, then we unblock rendering. All other DOM changes
are already handled by existing code.

This patch also adds new WPT tests for the behavior.

Note: The spec does not require such behavior -- it only requires when
the UA must not render, but there's no requirement of when the UA must
render. So the tests are marked as "optional".

Bug: 1271296
Change-Id: Iead14b73014370ea72e6eeb6714b75cc56de974f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3601726
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#995853}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants