Closed
Bug 1620873
Opened 4 years ago
Closed 4 years ago
Move MotionPathData in TransformData
Categories
(Core :: Layout, task, P3)
Core
Layout
Tracking
()
RESOLVED
FIXED
mozilla76
Tracking | Status | |
---|---|---|
firefox76 | --- | fixed |
People
(Reporter: hiro, Assigned: hiro)
References
Details
Attachments
(1 file)
If I remember correctly I did suggest to split MotionPathData from TransformData because normal transform animations don't need the MotionPathData at all. That said, having MotionPathData in Animation is odd, so probably what we want to do is;
struct TransformData {
...
MoationPathData? motionPathData;
}
Assignee | ||
Comment 2•4 years ago
|
||
Having MotionPathData in layers::Animation is a bit inefficient for animations
other than transform like properties.
Pushed by hikezoe.birchill@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7b6356b842a5 Make MotionPathData Maybe<MotionPathData> in TransformData. r=boris
Comment 4•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox76:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
You need to log in
before you can comment on or make changes to this bug.
Description
•