Apply offset-position to ray()
Categories
(Core :: CSS Transitions and Animations, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox116 | --- | fixed |
People
(Reporter: boris, Assigned: boris)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-complete)
Attachments
(4 files)
offset-position
should be applied to ray() function.
Assignee | ||
Comment 2•1 year ago
|
||
It's unnecessary to implement ToAnimatedZero for this property and so we
return Err(()), just like other properties which also use basic shapes,
e.g. clip-path, shape-outside.
Assignee | ||
Comment 3•1 year ago
|
||
We reuse PositionOrAuto here, and let "auto" represent the situation when the
author omits "at <position>" because it has a special meaning.
https://drafts.fxtf.org/motion-1/#valdef-ray-at-position
Note: No need to update css/motion/parsing/offset-path-parsing-valid.html
because Blink added some to the upstream repo already.
Assignee | ||
Comment 4•1 year ago
|
||
We apply offset-position and "at <position>" to ray function. However,
only use it on the main thread. For compositor animation, we will finish
it in the following patches.
No need to add tests because there are tests in the WPT upstream repo already:
css/motion/offset-path-ray-011.html
css/motion/offset-path-ray-012.html
css/motion/offset-path-ray-013.html
css/motion/offset-path-ray-014.html
Those tests should cover what we do in this patch.
Assignee | ||
Comment 5•1 year ago
|
||
We send offset-position to the compositor, just like other similar
properties, e.g. offset-rotate, offset-anchor. This includes extracting
this animation value, doing serialization and sending it via IPC.
So now we can run the animation of ray() on the compositor properly.
Assignee | ||
Updated•1 year ago
|
Comment 8•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/1b4fccd6ecff
https://hg.mozilla.org/mozilla-central/rev/c9a0635b6d98
https://hg.mozilla.org/mozilla-central/rev/c53b5d507346
https://hg.mozilla.org/mozilla-central/rev/3a8e0dd854b5
Comment 10•1 year ago
|
||
Corresponding MDN doc updates can be tracked via this issue: https://github.com/mdn/content/issues/27751
Description
•