Progress bar eats 10% CPU

[dandv]

I wouldn't normally care, but it turned out that Semantic UI's progress bar caused my laptop fan to start spinning at http://semantic-ui.com/. After removing the progress bar, CPU utilization fell below the threshold.

Here's a screencast. It's a little slow to allow the CPU usage to stabilize.

Measured with Process Hacker on Windows 7 64-bit. Chrome 43.0.2357.81 m.

[jlukic]

From checking CPU profiling in chrome, seems like the blinking cursor and progress bar both have to be removed to get CPU usage down to 0. Kinda amazing how much CPU usage comes from a simple css transition.

I'll remove progress bar from homepage for sure. Blinking cursor I'll stop after animation.

[jlukic]

Ignore that commit, incorrectly tagged.

I've gone ahead and removed blinking cursor after animation finishes, and removed progress bar from homepage examples.

I still need to redo homepage for launch.

[lauri-elevant]

The latest version is still eating absurd amounts of CPU cycles for rendering this strange animation that does not seem to have any meaningful semantics to my mind. If you set the percentage of the progress bar to anything above 0, it starts this sweeping animation that is supposed to say that it is .. what exactly? :) I can't figure it out.

Nothing should be lost by adding:

    .ui.active.progress .bar::after {
      -webkit-animation: none !important;
      animation: none !important;
    }

Before and after:

Even if the animation does carry some useful meaning, I'd argue that the cost of it should also be factored in.