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

Don't unblock rendering for implicitly render-blocking elements on blocking attribute changes #7857

Merged
merged 2 commits into from
Apr 27, 2022

Conversation

xiaochengh
Copy link
Contributor

@xiaochengh xiaochengh commented Apr 26, 2022

source Show resolved Hide resolved
source Show resolved Hide resolved
source Show resolved Hide resolved
source Show resolved Hide resolved
source Show resolved Hide resolved
Copy link
Contributor Author

@xiaochengh xiaochengh left a comment

Choose a reason for hiding this comment

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

Thanks for reviewing! PR updated.

source Show resolved Hide resolved
source Show resolved Hide resolved
source Show resolved Hide resolved
source Show resolved Hide resolved
@xiaochengh xiaochengh marked this pull request as ready for review April 26, 2022 19:42
@xiaochengh
Copy link
Contributor Author

Friendly ping :)

@domenic domenic merged commit a2a74be into whatwg:main Apr 27, 2022
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this pull request Apr 27, 2022
…attribute is removed

1. This patch adds tests for whatwg/html#7857.
   When `blocking=render` is removed, if the element is implicitly
   render-blocking, we shouldn't unblock rendering for it.

2. This patch fixes how <link> element respond to `blocking` attribute
   changes. Previously, the element simply reprocesses (cancel and then
   restart) on every `blocking` attribute change, causing unnecessary
   work and also some bugs on stylesheets. This patch changes that into
   unblock rendering if needed to match the spec.

Bug: 1271296
Change-Id: I54a2f33dc1ed9971eaeceeb677a165d598d5d4d1
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this pull request Apr 28, 2022
…attribute is removed

1. This patch adds tests for whatwg/html#7857.
   When `blocking=render` is removed, if the element is implicitly
   render-blocking, we shouldn't unblock rendering for it.

2. This patch fixes how <link> element respond to `blocking` attribute
   changes. Previously, the element simply reprocesses (cancel and then
   restart) on every `blocking` attribute change, causing unnecessary
   work and also some bugs on stylesheets. This patch changes that into
   unblock rendering if needed to match the spec.

Bug: 1271296
Change-Id: I54a2f33dc1ed9971eaeceeb677a165d598d5d4d1
aarongable pushed a commit to chromium/chromium that referenced this pull request May 2, 2022
…attribute is removed

1. This patch adds tests for whatwg/html#7857.
   When `blocking=render` is removed, if the element is implicitly
   render-blocking, we shouldn't unblock rendering for it.

2. This patch fixes how <link> element respond to `blocking` attribute
   changes. Previously, the element simply reprocesses (cancel and then
   restart) on every `blocking` attribute change, causing unnecessary
   work and also some bugs on stylesheets. This patch changes that into
   unblock rendering if needed to match the spec.

Bug: 1271296
Change-Id: I54a2f33dc1ed9971eaeceeb677a165d598d5d4d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3608747
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#998568}
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this pull request May 2, 2022
…attribute is removed

1. This patch adds tests for whatwg/html#7857.
   When `blocking=render` is removed, if the element is implicitly
   render-blocking, we shouldn't unblock rendering for it.

2. This patch fixes how <link> element respond to `blocking` attribute
   changes. Previously, the element simply reprocesses (cancel and then
   restart) on every `blocking` attribute change, causing unnecessary
   work and also some bugs on stylesheets. This patch changes that into
   unblock rendering if needed to match the spec.

Bug: 1271296
Change-Id: I54a2f33dc1ed9971eaeceeb677a165d598d5d4d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3608747
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#998568}
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this pull request May 2, 2022
…attribute is removed

1. This patch adds tests for whatwg/html#7857.
   When `blocking=render` is removed, if the element is implicitly
   render-blocking, we shouldn't unblock rendering for it.

2. This patch fixes how <link> element respond to `blocking` attribute
   changes. Previously, the element simply reprocesses (cancel and then
   restart) on every `blocking` attribute change, causing unnecessary
   work and also some bugs on stylesheets. This patch changes that into
   unblock rendering if needed to match the spec.

Bug: 1271296
Change-Id: I54a2f33dc1ed9971eaeceeb677a165d598d5d4d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3608747
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#998568}
@xiaochengh xiaochengh deleted the issue7856 branch May 3, 2022 18:02
moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this pull request May 16, 2022
…ender-blocking when blocking attribute is removed, a=testonly

Automatic update from web-platform-tests
[renderblocking] Don't cancel implicit render-blocking when blocking attribute is removed

1. This patch adds tests for whatwg/html#7857.
   When `blocking=render` is removed, if the element is implicitly
   render-blocking, we shouldn't unblock rendering for it.

2. This patch fixes how <link> element respond to `blocking` attribute
   changes. Previously, the element simply reprocesses (cancel and then
   restart) on every `blocking` attribute change, causing unnecessary
   work and also some bugs on stylesheets. This patch changes that into
   unblock rendering if needed to match the spec.

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

--

wpt-commits: 4de4be2a2204e4349b36dce25a9d648aba4fbf11
wpt-pr: 33798
zcorpan pushed a commit that referenced this pull request May 16, 2022
jamienicol pushed a commit to jamienicol/gecko that referenced this pull request May 25, 2022
…ender-blocking when blocking attribute is removed, a=testonly

Automatic update from web-platform-tests
[renderblocking] Don't cancel implicit render-blocking when blocking attribute is removed

1. This patch adds tests for whatwg/html#7857.
   When `blocking=render` is removed, if the element is implicitly
   render-blocking, we shouldn't unblock rendering for it.

2. This patch fixes how <link> element respond to `blocking` attribute
   changes. Previously, the element simply reprocesses (cancel and then
   restart) on every `blocking` attribute change, causing unnecessary
   work and also some bugs on stylesheets. This patch changes that into
   unblock rendering if needed to match the spec.

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

--

wpt-commits: 4de4be2a2204e4349b36dce25a9d648aba4fbf11
wpt-pr: 33798
mfreed7 pushed a commit to mfreed7/html that referenced this pull request Jun 3, 2022
mjfroman pushed a commit to mjfroman/moz-libwebrtc-third-party that referenced this pull request Oct 14, 2022
This change reflects the renaming of "render-blocking" to
"explicitly render-blocking" in whatwg/html#7857

It's also a preparation for implementing logic related to
"implicitly render-blocking" in crrev.com/c/3608747

Bug: 1271296
Change-Id: I6724e7e4858e2b2c92398b8ff68c984f793a4753
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3607827
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Auto-Submit: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#997335}
NOKEYCHECK=True
GitOrigin-RevId: c1bcf0dcb6b206e42c82c515d89466133bddc045
mjfroman pushed a commit to mjfroman/moz-libwebrtc-third-party that referenced this pull request Oct 14, 2022
…attribute is removed

1. This patch adds tests for whatwg/html#7857.
   When `blocking=render` is removed, if the element is implicitly
   render-blocking, we shouldn't unblock rendering for it.

2. This patch fixes how <link> element respond to `blocking` attribute
   changes. Previously, the element simply reprocesses (cancel and then
   restart) on every `blocking` attribute change, causing unnecessary
   work and also some bugs on stylesheets. This patch changes that into
   unblock rendering if needed to match the spec.

Bug: 1271296
Change-Id: I54a2f33dc1ed9971eaeceeb677a165d598d5d4d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3608747
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#998568}
NOKEYCHECK=True
GitOrigin-RevId: 831456d6a2d55d251875cdf15de4066e66d817e9
foolip added a commit to web-platform-tests/wpt that referenced this pull request Nov 14, 2023
These tests were added in these PRs:
#32553
#32669
#32703
#32809
#33291
#33798

These were developed against HTML PRs which are now merged:
whatwg/html#7474
whatwg/html#7603
whatwg/html#7857
moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this pull request Nov 22, 2023
…r tentative, a=testonly

Automatic update from web-platform-tests
Mark most render-blocking tests no longer tentative (#43113)

These tests were added in these PRs:
web-platform-tests/wpt#32553
web-platform-tests/wpt#32669
web-platform-tests/wpt#32703
web-platform-tests/wpt#32809
web-platform-tests/wpt#33291
web-platform-tests/wpt#33798

These were developed against HTML PRs which are now merged:
whatwg/html#7474
whatwg/html#7603
whatwg/html#7857
--

wpt-commits: aa6bdcbb00f30914b87794cf82b015fc02d4cc5b
wpt-pr: 43113
moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this pull request Nov 22, 2023
…r tentative, a=testonly

Automatic update from web-platform-tests
Mark most render-blocking tests no longer tentative (#43113)

These tests were added in these PRs:
web-platform-tests/wpt#32553
web-platform-tests/wpt#32669
web-platform-tests/wpt#32703
web-platform-tests/wpt#32809
web-platform-tests/wpt#33291
web-platform-tests/wpt#33798

These were developed against HTML PRs which are now merged:
whatwg/html#7474
whatwg/html#7603
whatwg/html#7857
--

wpt-commits: aa6bdcbb00f30914b87794cf82b015fc02d4cc5b
wpt-pr: 43113
vinnydiehl pushed a commit to vinnydiehl/mozilla-unified that referenced this pull request Nov 24, 2023
…r tentative, a=testonly

Automatic update from web-platform-tests
Mark most render-blocking tests no longer tentative (#43113)

These tests were added in these PRs:
web-platform-tests/wpt#32553
web-platform-tests/wpt#32669
web-platform-tests/wpt#32703
web-platform-tests/wpt#32809
web-platform-tests/wpt#33291
web-platform-tests/wpt#33798

These were developed against HTML PRs which are now merged:
whatwg/html#7474
whatwg/html#7603
whatwg/html#7857
--

wpt-commits: aa6bdcbb00f30914b87794cf82b015fc02d4cc5b
wpt-pr: 43113
vinnydiehl pushed a commit to vinnydiehl/mozilla-unified that referenced this pull request Nov 24, 2023
…r tentative, a=testonly

Automatic update from web-platform-tests
Mark most render-blocking tests no longer tentative (#43113)

These tests were added in these PRs:
web-platform-tests/wpt#32553
web-platform-tests/wpt#32669
web-platform-tests/wpt#32703
web-platform-tests/wpt#32809
web-platform-tests/wpt#33291
web-platform-tests/wpt#33798

These were developed against HTML PRs which are now merged:
whatwg/html#7474
whatwg/html#7603
whatwg/html#7857
--

wpt-commits: aa6bdcbb00f30914b87794cf82b015fc02d4cc5b
wpt-pr: 43113
gecko-dev-updater pushed a commit to marco-c/gecko-dev-wordified-and-comments-removed that referenced this pull request Nov 30, 2023
…r tentative, a=testonly

Automatic update from web-platform-tests
Mark most render-blocking tests no longer tentative (#43113)

These tests were added in these PRs:
web-platform-tests/wpt#32553
web-platform-tests/wpt#32669
web-platform-tests/wpt#32703
web-platform-tests/wpt#32809
web-platform-tests/wpt#33291
web-platform-tests/wpt#33798

These were developed against HTML PRs which are now merged:
whatwg/html#7474
whatwg/html#7603
whatwg/html#7857
--

wpt-commits: aa6bdcbb00f30914b87794cf82b015fc02d4cc5b
wpt-pr: 43113

UltraBlame original commit: 58cb91eda01d9227e0e02791aa6562da04967a42
gecko-dev-updater pushed a commit to marco-c/gecko-dev-comments-removed that referenced this pull request Nov 30, 2023
…r tentative, a=testonly

Automatic update from web-platform-tests
Mark most render-blocking tests no longer tentative (#43113)

These tests were added in these PRs:
web-platform-tests/wpt#32553
web-platform-tests/wpt#32669
web-platform-tests/wpt#32703
web-platform-tests/wpt#32809
web-platform-tests/wpt#33291
web-platform-tests/wpt#33798

These were developed against HTML PRs which are now merged:
whatwg/html#7474
whatwg/html#7603
whatwg/html#7857
--

wpt-commits: aa6bdcbb00f30914b87794cf82b015fc02d4cc5b
wpt-pr: 43113

UltraBlame original commit: 58cb91eda01d9227e0e02791aa6562da04967a42
gecko-dev-updater pushed a commit to marco-c/gecko-dev-wordified that referenced this pull request Nov 30, 2023
…r tentative, a=testonly

Automatic update from web-platform-tests
Mark most render-blocking tests no longer tentative (#43113)

These tests were added in these PRs:
web-platform-tests/wpt#32553
web-platform-tests/wpt#32669
web-platform-tests/wpt#32703
web-platform-tests/wpt#32809
web-platform-tests/wpt#33291
web-platform-tests/wpt#33798

These were developed against HTML PRs which are now merged:
whatwg/html#7474
whatwg/html#7603
whatwg/html#7857
--

wpt-commits: aa6bdcbb00f30914b87794cf82b015fc02d4cc5b
wpt-pr: 43113

UltraBlame original commit: 58cb91eda01d9227e0e02791aa6562da04967a42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

Removing blocking=render from "implicitly render-blocking" elements unblocks rendering
2 participants