Open Bug 1997284 Opened 22 days ago Updated 14 days ago

New wpt failures in /css/css-borders/tentative/parsing/border-shape-computed.html

Categories

(Core :: CSS Parsing and Computation, defect)

defect

Tracking

()

People

(Reporter: wpt-sync, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [wpt])

Syncing wpt PR 55628 found new untriaged test failures in CI

Tests Affected

New Tests That Don't Pass

  • /css/css-borders/tentative/parsing/border-shape-computed.html [wpt.fyi]
    • Property border-shape value 'circle() content-box': FAIL (Chrome: PASS, Safari: FAIL)
    • Property border-shape value 'circle() border-box polygon(10px 10px, 100px 10px, 10px 100px) border-box': FAIL (Chrome: PASS, Safari: FAIL)
    • Property border-shape value 'circle() padding-box polygon(10px 10px, 100px 10px, 10px 100px) border-box': FAIL (Chrome: PASS, Safari: FAIL)
    • Property border-shape value 'circle() padding-box polygon(10px 10px, 100px 10px, 10px 100px) padding-box': FAIL (Chrome: PASS, Safari: FAIL)
    • Property border-shape value 'circle() polygon(10px 10px, 100px 10px, 10px 100px) border-box': FAIL (Chrome: PASS, Safari: FAIL)
    • Property border-shape value 'circle() polygon(10px 10px, 100px 10px, 10px 100px) content-box': FAIL (Chrome: PASS, Safari: FAIL)

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

These updates will be on mozilla-central once bug 1996114 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.

Blocks: 1982766
Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.