Closed
Bug 1591629
Opened 5 years ago
Closed 4 years ago
No need to pass TransformData for all transform-like properties to compositor
Categories
(Core :: CSS Transitions and Animations, enhancement, P3)
Core
CSS Transitions and Animations
Tracking
()
RESOLVED
FIXED
mozilla74
Tracking | Status | |
---|---|---|
firefox74 | --- | fixed |
People
(Reporter: boris, Assigned: boris)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
We can reduce the usage of data we pass via IPC LayersMessages by
- Use an individual struct for motion path data (i.e.
MotionPathData
). If there is nooffset-*
, we just set it Nothing(). (This may not have benefits on data usage because Maybe<> still allocate space it may need.) But still worth to do. - Don't pass
TransformData
andMotionPathData
for all transform-like properties. (Note: All of them for the same transaction are the same). Maybe only pass it with the first animation property. - Maybe we can remove any potential duplicates from TransformData or MotionPathData. Or maybe not.
Assignee | ||
Comment 1•4 years ago
|
||
The benefit are:
- For the rest
layers::Animation
s, theirTransformData
areNothing()
,
so we can avoid any posisible copy. - In the compositor,
PropertyAniamtionGroup
usesUniquePtr
to hold the
TransformData
in the first element, and the rest elements don't need
to copy/allocalate memery for this duplicated data.
Assignee | ||
Comment 2•4 years ago
|
||
So we don't need to create motion path data if there is no offset-path style
and no animations of offset-path.
Assignee | ||
Comment 3•4 years ago
|
||
To avoid the ambiguous name because we also have layers::MotionPathData.
Pushed by boris.chiou@gmail.com: https://hg.mozilla.org/integration/autoland/rev/e9462ce8f669 Keep TransformData only in the first element when passing animation data through IPC. r=hiro https://hg.mozilla.org/integration/autoland/rev/88869acebf28 Split TransformData into 2 parts - transform data and motion path data. r=hiro https://hg.mozilla.org/integration/autoland/rev/3b89f8acd826 Rename mozilla::MotionPathData as mozilla::ResolvedMotionPathData. r=hiro
Comment 5•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/e9462ce8f669
https://hg.mozilla.org/mozilla-central/rev/88869acebf28
https://hg.mozilla.org/mozilla-central/rev/3b89f8acd826
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox74:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla74
You need to log in
before you can comment on or make changes to this bug.
Description
•