(In reply to Hiroyuki Ikezoe (:hiro) from comment #10) > Note that, !import transform property shouldn't stop running motion path properties on the compositor, I think. I maybe missing something though. Just like this test [1] and the current implementation [2], we have to merge transform property, individual transform properties, and motion path transform properties all together to get the final transform matrix. This means we have to make sure all of their animations are running on the same thread. If any of them cannot run on the compositor, we have to fall back to main thread. [1] https://searchfox.org/mozilla-central/rev/e18057a9613ffda06dfd3640209ca234ed7dc37d/dom/animation/test/chrome/test_running_on_compositor.html#1118-1143 [2] https://searchfox.org/mozilla-central/rev/e18057a9613ffda06dfd3640209ca234ed7dc37d/dom/animation/KeyframeEffect.cpp#1504-1520
Bug 1484780 Comment 11 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Hiroyuki Ikezoe (:hiro) from comment #10) > Note that, !import transform property shouldn't stop running motion path properties on the compositor, I think. I maybe missing something though. Just like this test [1] and the current implementation [2], we have to merge transform property, individual transform properties, and motion path transform properties all together to get the final transform matrix. This means we have to make sure all of them are on the same thread. If any of them cannot run on the compositor, we have to fall back to main thread. [1] https://searchfox.org/mozilla-central/rev/e18057a9613ffda06dfd3640209ca234ed7dc37d/dom/animation/test/chrome/test_running_on_compositor.html#1118-1143 [2] https://searchfox.org/mozilla-central/rev/e18057a9613ffda06dfd3640209ca234ed7dc37d/dom/animation/KeyframeEffect.cpp#1504-1520