Hacker News new | ask | show | jobs
by editkid 2125 days ago
Hello! I'm a developer for Klim. Thanks for prompting us to look at this CPU usage issue. I'm happy to say that it has now been resolved.

For those interested in the underlying cause, it seems to have been a bug in Safari. The following CSS triggered infinite repaints:

  transition: all;
The solution was to simply be more specific:

  transition: background-color;
1 comments

Interesting cause. I wonder how long we’ll need to manually specify what transitions. It seems like an optimization problem that the browser could solve on its own, but I guess not yet.
Here is the related bug report. It's quite a specific case, so not simply triggered by using "transition: all" in isolation.

https://bugs.webkit.org/show_bug.cgi?id=202467

Great detective work.