New wpt failures in /css/motion/parsing/offset-path-computed.html
Categories
(Core :: SVG, defect)
Tracking
()
People
(Reporter: wpt-sync, Unassigned)
References
Details
(Whiteboard: [wpt])
Syncing wpt PR 31658 found new untriaged test failures in CI
Tests Affected
New Tests That Don't Pass
/css/motion/parsing/offset-path-computed.html
Property offset-path value 'path("m 20 0 h -100")': FAIL (Chrome: PASS, Safari: FAIL)
Property offset-path value 'path("m 10 20 q 30 60 40 50 q 100 70 90 80")': FAIL (Chrome: PASS, Safari: FAIL)
Property offset-path value 'path("M 0 0 L 100 100 m 0 100 l 100 0 Z l 160 20 Z")': FAIL (Chrome: PASS, Safari: FAIL)
Property offset-path value 'path("m 10 20 l 20 30 Z l 50 60 Z m 70 80 l 90 60 Z t 70 120")': FAIL (Chrome: PASS, Safari: FAIL)
Property offset-path value 'path("m 10 170 h 90 v 30 m 0 0 s 1 2 3 4 z c 9 8 7 6 5 4")': FAIL (Chrome: PASS, Safari: FAIL)
Property offset-path value 'path("m 10 20 a 10 20 30 1 0 40 50 a 110 120 30 1 1 140 50")': FAIL (Chrome: PASS, Safari: FAIL)
CI Results
Gecko CI (Treeherder)
GitHub PR Head
Notes
These updates will be on mozilla-central once bug 1741627 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•3 years ago
|
||
I don't think the tests are valid, as per spec text, the computed vaule of offset-path should be the specified value. Or I am missing something. CCing Boris.
Comment 2•3 years ago
|
||
This is related to the spec issue: https://github.com/w3c/svgwg/issues/321, related to Bug 1489392. No plan now until the spec gets updated.
Comment 3•2 years ago
|
||
Boris, is this spec up to date and this is included in with Motion Path work?
Comment 4•2 years ago
|
||
The is related to the spec issue: github.com/w3c/svgwg/issues/321. There is no resolution for now, and we updated tests in Bug 1489392 already. So let's close this bug.
Updated•2 years ago
|
Description
•