Closed Bug 1653439 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 24639 - Add iframe loading=lazy data: and Blob URL WPTs

Categories

(Core :: DOM: Core & HTML, task, P4)

task

Tracking

()

RESOLVED FIXED
mozilla80
Tracking Status
firefox80 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 24639 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/24639
Details from upstream follow.

Dominic Farolino <dom@chromium.org> wrote:

Add iframe loading=lazy data: and Blob URL WPTs

R=sclittle@chromium.org

Bug: 1047909
Change-Id: Ic5e1ef207e8483ae1a56a4ee090d7ad6317a3a3f

Reviewed-on: https://chromium-review.googlesource.com/2303859
WPT-Export-Revision: a1e52d9c2316325e24dfc24f941992ef7f0dedb7

PR 24639 applied with additional changes from upstream: 2e5721c4ac9dedb02bc6ac965fdf511b2d30e467
Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

Ran 12 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 5 subtests

Status Summary

Firefox

OK : 1
PASS: 1
FAIL: 4

Chrome

OK : 1
PASS: 2
FAIL: 3

Safari

OK : 1
PASS: 1
FAIL: 4

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/html/semantics/embedded-content/the-iframe-element/iframe-loading-lazy.html
Below-viewport blob url iframes load lazily: FAIL (Chrome: FAIL, Safari: FAIL)
Below-viewport data: url iframes load lazily: FAIL (Chrome: FAIL, Safari: FAIL)
Below-viewport iframes load lazily: FAIL (Chrome: PASS, Safari: FAIL)
Below-viewport srcdoc iframes load lazily: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/710de7f64f23 [wpt PR 24639] - Add iframe loading=lazy data: and Blob URL WPTs, a=testonly
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
You need to log in before you can comment on or make changes to this bug.