Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Default CSS for <progress> element causes CPU to spike. #6646

Closed
@bolinfest

Description

This is on OS X, version 10.10.3 (Yosemite).

As shown in the animated GIF, enabling the following CSS style (which is present for <progress> elements) causes the CPU usage to spike:

-webkit-animation: animate-stripes 5s linear infinite;

From the Chrome profiling tools, you can see that all of the <progress> elements are being redrawn continuously while this CSS is being applied. Once it is removed, the CPU usage goes back down to zero and the redraw ends.

Outright removing this style only affects the display of indeterminate progress bars, as they appear to be designed to have a "barber poll" animation.

Something should be done so that package developers who introduce the use of a <progress> element do not inadvertently burn CPU.

progress-causes-cpu-spike

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions