Bugzilla

Basically, Gecko supports `opacity`, `transform`, `translate`, `rotate`, `scale`, `offset` (i.e. motion-path), and `background-color` animations running on the compositor thread.

Besides, it seems Blink and WebKit support other properties, e.g. filter, backdrop-filter, running off-main thread animations, and looks like some other people have interests in making more CSS properties support compositor animations, based on the empirical data which shows how often Web pages do this: https://www.chromestatus.com/metrics/css/animated. This could be the meta bug to trace these issues and any potential improvement.

Basically, Gecko supports `opacity`, `transform`, `translate`, `rotate`, `scale`, `offset` (i.e. motion-path), and `background-color` animations running on the compositor thread.

Besides, it seems Blink and WebKit support other properties, e.g. `filter`, `backdrop-filter`, running off-main thread animations, and looks like some other people have interests in making more CSS properties support compositor animations, based on the empirical data which shows how often Web pages do this: https://www.chromestatus.com/metrics/css/animated. This could be the meta bug to trace these issues and any potential improvement.

Basically, Gecko supports `opacity`, `transform`, `translate`, `rotate`, `scale`, `offset` (i.e. motion-path), and `background-color` animations running on the compositor thread.

Besides, it seems [Blink](https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/animation/compositor_animations.cc?type=cs&sq=package:chromium&g=0&l=693-754) and WebKit support other properties, e.g. `filter`, `backdrop-filter`, running off-main thread animations, and looks like some other people have interests in making more CSS properties support compositor animations, based on the empirical data which shows how often Web pages do this: https://www.chromestatus.com/metrics/css/animated. This could be the meta bug to trace these issues and any potential improvement.