- From: Majid Valipour via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 Sep 2018 19:14:30 +0000
- To: public-houdini-archive@w3.org
> Gecko differentiates between different types of properties. If you are animating two geometric properties--e.g. 'width' and 'transform'--with the same animation (or even in different animations but with the same starting time) and one can't be run on the compositor, we run both of them on the main thread. If you're animating background-color and transform, however, we'll happily do background-color on the main thread and transform on the compositor. This is great. I made a [small demo](https://jsbin.com/fozizir/edit?css,output) that showcases this. In Firefox only background janks but in Chrome both background and transform jank. The fact that Firefox has shipped this already is a good sign that we should follow. @flackr has previously advocated that we should even go further and allow unsynchronized updates for all properties ([demo](http://jsbin.com/dufako/2/edit?html,css,js,output)). @birtles can you share the thinking behind why Gecko have chosen to always keep geometric properties in sync? -- GitHub Notification of comment by majido Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/805#issuecomment-420027577 using your GitHub account
Received on Monday, 10 September 2018 19:14:31 UTC