[wpt-sync] Sync PR 33145 - [renderblocking] Implement render-blocking on script elements
Categories
(Core :: DOM: Core & HTML, task, P4)
Tracking
()
Tracking | Status | |
---|---|---|
firefox100 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 33145 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/33145
Details from upstream follow.
Xiaocheng Hu <xiaochengh@chromium.org> wrote:
[renderblocking] Implement render-blocking on script elements
This patch makes RenderBlockingResourceManager to accept scripts as
render-blocking resources, and implements the following parts of the
spec:
- Right before fetching a render-blocking script, add it to
RenderBlockingResourceManager:https://html.spec.whatwg.org/multipage/scripting.html#script-processing-model:block-rendering
- When executing a script, remove it from RenderBlockingResourceManager
https://html.spec.whatwg.org/multipage/scripting.html#script-processing-model:unblock-rendering
- When a render-blocking script is removed, also remove it from
RenderBlockingResourceManager, so that rendering is unblocked even
without executing the script:https://html.spec.whatwg.org/multipage/urls-and-fetching.html#blocking-attributes:unblock-rendering
Bug: 1271296
Change-Id: Ib5d7391668efb1a0c74a3c152e02c1b533accc43
Reviewed-on: https://chromium-review.googlesource.com/3511116
WPT-Export-Revision: 858eb996f39af40f79a68e36c69d9205f5e3ef34
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
Assignee | ||
Comment 2•3 years ago
|
||
Assignee | ||
Comment 3•3 years ago
|
||
CI Results
Ran 12 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 1 tests and 1 subtests
Status Summary
Firefox
OK : 1
PASS: 1
Chrome
OK : 1
PASS: 1
Safari
OK : 1
PASS: 1
Links
Comment 6•3 years ago
|
||
bugherder |
Description
•