Closed
Bug 1367290
Opened 7 years ago
Closed 7 years ago
stylo: transition is slower than gecko on the CSS Creates demo
Categories
(Core :: CSS Parsing and Computation, defect, P1)
Tracking
()
RESOLVED
DUPLICATE
of bug 1367292
People
(Reporter: shinglyu, Assigned: hiro)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
STR: * Open http://bennettfeely.com/csscreatures/ * Observe the ones with bouncy movements * Click the faces Expected: * Smooth animation * When clicked, the ball will expand for a short period of time Actual: * Stylo's animation has significantly lower frame rate the gecko * No animation when clicked Version: * commit 20ab6785cbd9da0af89da357cbef4f50c6a2afdf * opt build on linux64
Reporter | ||
Comment 1•7 years ago
|
||
Comment 2•7 years ago
|
||
From which day is the build? I know we enabled OMTA literally two days ago (bug 1334036). I assume there's a lot of difference potentially related to that.
Assignee | ||
Comment 3•7 years ago
|
||
Yeah, exactly. But unfortunately it might be unrelated to. I see below warnings; Animation of ‘transform’ cannot be run on the compositor because it should be synchronized with animations of geometric properties that started at the same time [div]
Assignee | ||
Updated•7 years ago
|
Summary: stylo: transition is slower then gecko on the CSS Creates demo → stylo: transition is slower than gecko on the CSS Creates demo
Updated•7 years ago
|
Assignee: nobody → hikezoe
Priority: -- → P1
Assignee | ||
Comment 4•7 years ago
|
||
The transition property is: "transition: .3s cubic-bezier(.15,.60,.30,1.9)". We might be slower in case of "transition-property: all". Another possibility is that if the transition is *NOT* started by clicking the element, it might be related to bug 1328505.
Assignee | ||
Updated•7 years ago
|
Assignee | ||
Comment 5•7 years ago
|
||
OK, I think this is because of mismatched transform list animations.
Depends on: 1365851
Assignee | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•