New wpt failures in /css/css-shapes/shape-outside/ [values/shape-outside-shape-arguments-000.html, shape-box/shape-outside-border-box-003.html, shape-box/shape-outside-content-box-003.html, and 1 others]
Categories
(Core :: Layout: Floats, defect, P3)
Tracking
()
People
(Reporter: wpt-sync, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [wpt])
Syncing wpt PR 53444 found new untriaged test failures in CI
Tests Affected
Firefox-only failures
- /css/css-shapes/shape-outside/values/shape-outside-shape-arguments-000.html [wpt.fyi]
- View relative units - computed:
FAIL
- View relative units - computed:
- /css/css-shapes/shape-outside/shape-box/shape-outside-border-box-003.html [wpt.fyi]:
FAIL - /css/css-shapes/shape-outside/shape-box/shape-outside-content-box-003.html [wpt.fyi]:
FAIL - /css/css-shapes/shape-outside/shape-box/shape-outside-padding-box-003.html [wpt.fyi]:
FAIL
CI Results
Missing results from treeherder
GitHub PR Head
Notes
These updates will be on mozilla-central once bug 1976337 lands.
Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.
This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/
If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.
Comment 1•1 year ago
|
||
Jonathan, the first one seems unrelated (bug 1980223), but the other reftest failures does look like a result of your changes (might be that the fonts are different or something? doesn't seem like an incremental layout bug, zooming in and out doesn't fix it)
Comment 2•1 year ago
|
||
According to hg log testing/web-platform/meta/css/css-shapes/shape-outside/shape-box/shape-outside-border-box-003.html.ini, this is an expected failure since bug 1760395 (March 2022), so I'm not sure why it's being flagged as "new" now. The test fails, sure; but it's not new.
Description
•