Animated widget keeps frame clock running even when not rendered (non-visible stack widget)
Submitted by Josh Triplett
A widget with a CSS animation, such as GtkSpinner, will continue to update that animation (e.g. changing -gtk-icon-transform) and keep the frame clock active even if that widget sits in a stack and the stack has some other widget as the visible child.
For example, gnome-control-center's wifi panel creates a spinner, sets it to active and leaves it that way, puts it in a stack, and changes the visible child of that stack. Even when the spinner isn't the visible child, the frame clock stays active and wakes the system up 60 times a second.
Yes, gnome-control-center could set active to FALSE on the spinner. But it shouldn't have to, and fixing this would likely reduce wakeups in multiple applications.
Note: I've also seen 60fps wakeups in other applications, including quodlibet, that appear caused by the frame clock, but I haven't root-caused those yet.