It kind of surprises me that this is an issue at all. I was under the impression a large number of FF devs use Macbooks.
> UNCONFIRMED
> Votes: 0 votes
The discussion is all specific to that page. The biggest issue is that the animations are being driven from Javascript instead of CSS, so there's little we can do to optimize it.
The rest of the discussion is possible heuristics we can implement to optimize how we layerize the page. It would potentially help on this page, but might make things slower elsewhere.
That bug refers to high cpu load on that page. On that page it is due to the animation being driven from javascript.
If a simple CSS animation causes high cpu usage please file a separate bug with an attached test case.
Don’t you think it’s more likely there is a bug in macOS-specific Firefox code?
If I had to guess I would chalk it up to a qc issue on some Apple specific chipset that just doesn't get hit by the other browsers code paths and just doesn't get noticed in other less used, less intensive apps.
How to diagnose it or work around it is beyond me.