Closed
Bug 1818366
Opened 2 years ago
Closed 2 years ago
[wpt-sync] Sync PR 38662 - [css-images] [image-set] Don't expect an image to render if there are no
Categories
(Core :: Layout: Images, Video, and HTML Frames, task, P4)
Core
Layout: Images, Video, and HTML Frames
Tracking
()
RESOLVED
FIXED
112 Branch
Tracking | Status | |
---|---|---|
firefox112 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
(Depends on 1 open bug, )
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 38662 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/38662
Details from upstream follow.
Ryan Reno <rreno@apple.com> wrote:
[css-images] [image-set] Don't expect an image to render if there are no
supported types in the image-set
If the image-set does not contain any images with a supported MIME type the image set is valid but empty. In that case we shouldn't expect any image to render.
See https://github.com/w3c/csswg-drafts/issues/8266 for discussion.
Assignee | ||
Updated•2 years ago
|
Component: web-platform-tests → Layout: Images, Video, and HTML Frames
Product: Testing → Core
Assignee | ||
Comment 1•2 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=5f1f3fa440716ba074ea40cdaf8c8e2cae17340f
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/61df1be3aa5d
[wpt PR 38662] - [image-set] Don't expect an image to render if there are no supported types in the image-set, a=testonly
https://hg.mozilla.org/integration/autoland/rev/0c22935e9a7d
[wpt PR 38662] - Update wpt metadata, a=testonly
Assignee | ||
Comment 3•2 years ago
|
||
Test result changes from PR not available.
Comment 4•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/61df1be3aa5d
https://hg.mozilla.org/mozilla-central/rev/0c22935e9a7d
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox112:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•