[wpt-sync] Sync PR 49659 - render blocking: Update tests to include ~250 bytes of text in divs
Categories
(Core :: DOM: Core & HTML, task, P4)
Tracking
()
Tracking | Status | |
---|---|---|
firefox135 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 49659 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/49659
Details from upstream follow.
Vladimir Levin <vmpstr@chromium.org> wrote:
render blocking: Update tests to include ~250 bytes of text in divs
This patch updates the element render blocking tests to include a blob
of text in divs to ensure that heuristics that avoid rAFs when there
is only empty divs is bypassed.Change-Id: I9ec0539707dfb36facaa5df964ac7e0aee7ec528
Reviewed-on: https://chromium-review.googlesource.com/6090257
WPT-Export-Revision: f67db95e2a01d92228b9fb76dd4f4086d22aef62
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Comment 1•2 months ago
|
||
Assignee | ||
Comment 2•2 months ago
|
||
CI Results
Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 38 tests and 1 subtests
Status Summary
Firefox
OK
: 38
PASS
: 23
FAIL
: 15
Chrome
OK
: 38
PASS
: 38
Safari
OK
: 38
PASS
: 37
FAIL
: 1
Links
Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base
Details
Firefox-only Failures
- /html/dom/render-blocking/element-render-blocking-001.html [wpt.fyi]
- blocking defers frames until full parsing:
FAIL
linked bug:Bug 1883569
- blocking defers frames until full parsing:
- /html/dom/render-blocking/element-render-blocking-002.html [wpt.fyi]
- blocking defers until needed element is parsed:
FAIL
- blocking defers until needed element is parsed:
- /html/dom/render-blocking/element-render-blocking-003.html [wpt.fyi]
- adding link in the head defers frames:
FAIL
linked bug:Bug 1883569
- adding link in the head defers frames:
- /html/dom/render-blocking/element-render-blocking-006.html [wpt.fyi]
- adding 'blocking=render' in the head makes it blocking:
FAIL
linked bug:Bug 1883569
- adding 'blocking=render' in the head makes it blocking:
- /html/dom/render-blocking/element-render-blocking-008.html [wpt.fyi]
- changing media to matching causes link to have an effect:
FAIL
linked bug:Bug 1883569
- changing media to matching causes link to have an effect:
- /html/dom/render-blocking/element-render-blocking-011.html [wpt.fyi]
- changing rel to expect in the head causes it to be blocking:
FAIL
linked bug:Bug 1883569
- changing rel to expect in the head causes it to be blocking:
- /html/dom/render-blocking/element-render-blocking-012.html [wpt.fyi]
- adding href in the head makes it blocking:
FAIL
linked bug:Bug 1883569
- adding href in the head makes it blocking:
- /html/dom/render-blocking/element-render-blocking-024.html [wpt.fyi]
- unknown href causes the whole document to be blocked:
FAIL
linked bug:Bug 1883569
- unknown href causes the whole document to be blocked:
- /html/dom/render-blocking/element-render-blocking-027.html [wpt.fyi]
- unknown href causes the whole document to be blocked (with href changes!):
FAIL
linked bug:Bug 1883569
- unknown href causes the whole document to be blocked (with href changes!):
- /html/dom/render-blocking/element-render-blocking-028.html [wpt.fyi]
- removing some links but not all keeps at least the matching link blocking:
FAIL
- removing some links but not all keeps at least the matching link blocking:
- /html/dom/render-blocking/element-render-blocking-034.html [wpt.fyi]
- relative URLs that match this document are OK:
FAIL
- relative URLs that match this document are OK:
- /html/dom/render-blocking/element-render-blocking-035.html [wpt.fyi]
- relative URLs that match this document are OK, regarless of <base>:
FAIL
- relative URLs that match this document are OK, regarless of <base>:
- /html/dom/render-blocking/element-render-blocking-037.html [wpt.fyi]
- relative URLs that match this document are OK, regarless of <base>:
FAIL
- relative URLs that match this document are OK, regarless of <base>:
- /html/dom/render-blocking/element-render-blocking-038.html [wpt.fyi]
- link rel=expect: only connected elements are eligible:
FAIL
- link rel=expect: only connected elements are eligible:
New Tests That Don't Pass
- /html/dom/render-blocking/element-render-blocking-001.html [wpt.fyi]
- blocking defers frames until full parsing:
FAIL
(Chrome:PASS
, Safari:PASS
)
- blocking defers frames until full parsing:
- /html/dom/render-blocking/element-render-blocking-002.html [wpt.fyi]
- blocking defers until needed element is parsed:
FAIL
(Chrome:PASS
, Safari:PASS
)
- blocking defers until needed element is parsed:
- /html/dom/render-blocking/element-render-blocking-003.html [wpt.fyi]
- adding link in the head defers frames:
FAIL
(Chrome:PASS
, Safari:PASS
)
- adding link in the head defers frames:
- /html/dom/render-blocking/element-render-blocking-006.html [wpt.fyi]
- adding 'blocking=render' in the head makes it blocking:
FAIL
(Chrome:PASS
, Safari:PASS
)
- adding 'blocking=render' in the head makes it blocking:
- /html/dom/render-blocking/element-render-blocking-008.html [wpt.fyi]
- changing media to matching causes link to have an effect:
FAIL
(Chrome:PASS
, Safari:PASS
)
- changing media to matching causes link to have an effect:
- /html/dom/render-blocking/element-render-blocking-011.html [wpt.fyi]
- changing rel to expect in the head causes it to be blocking:
FAIL
(Chrome:PASS
, Safari:PASS
)
- changing rel to expect in the head causes it to be blocking:
- /html/dom/render-blocking/element-render-blocking-012.html [wpt.fyi]
- adding href in the head makes it blocking:
FAIL
(Chrome:PASS
, Safari:PASS
)
- adding href in the head makes it blocking:
- /html/dom/render-blocking/element-render-blocking-024.html [wpt.fyi]
- unknown href causes the whole document to be blocked:
FAIL
(Chrome:PASS
, Safari:PASS
)
- unknown href causes the whole document to be blocked:
- /html/dom/render-blocking/element-render-blocking-027.html [wpt.fyi]
- unknown href causes the whole document to be blocked (with href changes!):
FAIL
(Chrome:PASS
, Safari:PASS
)
- unknown href causes the whole document to be blocked (with href changes!):
- /html/dom/render-blocking/element-render-blocking-028.html [wpt.fyi]
- removing some links but not all keeps at least the matching link blocking:
FAIL
(Chrome:PASS
, Safari:PASS
)
- removing some links but not all keeps at least the matching link blocking:
- /html/dom/render-blocking/element-render-blocking-033.html [wpt.fyi]
- blocking defers frames until full parsing:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- blocking defers frames until full parsing:
- /html/dom/render-blocking/element-render-blocking-034.html [wpt.fyi]
- relative URLs that match this document are OK:
FAIL
(Chrome:PASS
, Safari:PASS
)
- relative URLs that match this document are OK:
- /html/dom/render-blocking/element-render-blocking-035.html [wpt.fyi]
- relative URLs that match this document are OK, regarless of <base>:
FAIL
(Chrome:PASS
, Safari:PASS
)
- relative URLs that match this document are OK, regarless of <base>:
- /html/dom/render-blocking/element-render-blocking-037.html [wpt.fyi]
- relative URLs that match this document are OK, regarless of <base>:
FAIL
(Chrome:PASS
, Safari:PASS
)
- relative URLs that match this document are OK, regarless of <base>:
- /html/dom/render-blocking/element-render-blocking-038.html [wpt.fyi]
- link rel=expect: only connected elements are eligible:
FAIL
(Chrome:PASS
, Safari:PASS
)
- link rel=expect: only connected elements are eligible:
Description
•