Bug 204745
| Summary: | 100% CPU usage on transition with linear-gradient using CSS variables | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Derk-Jan Hartman <hartman.wiki> |
| Component: | Animations | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | dino, graouts, jonlee, koivisto, sabouhallawa, simon.fraser |
| Priority: | P2 | ||
| Version: | Safari 13 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Derk-Jan Hartman
Safari 15608.3.10.1.4
This is about the combination:
background: linear-gradient(300deg, var(--black-100) 0%, var(--black-100) 100%);
transition: .2s;
The following repro uses: 100%
https://codepen.io/hartman/pen/bGNGBKQ
This repro without CSS variables does not:
https://codepen.io/hartman/pen/JjojEgm
I'm assuming the variable breaks the 'no change/noop' detection and throws the transition into an endless update loop.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Simon Fraser (smfr)
I think this has been fixed. Can you try an Safari Tech Preview?
Derk-Jan Hartman
Seems so. Is this fix likely to land in a patch version of Safari as well, or do we have to wait for a March .1 release ?
I'm guessing a 100% CPU issue falls within some definitions of 'security fixes' ;)
Alexey Proskuryakov
Marking as configuration changed since it's fixed in WebKit.
We cannot comment on future Apple software releases.