You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I'm using aria-busy=true inside e.g. a div within dialog-tags, my web browser's processing resources skyrocket.
This does not happen if the aria-busy=true-animation is happening without the dialog involved.
Expected Behavior
Such a basic animation like aria-busy=true should not use up all available CPU resources but run smoothly at no cost.
Oh, ok. Long shot, as I still see this: I'm running my web browsers sandboxed (linux namespaces) - this includes them having limited or no direct access to hardware, probably including graphics acceleration (what comes to mind is e.g. /dev/dri/*).
Might be I misinterpreted it as an issue in picocss, while it affects all kinds of (combinations of) animations / blurs.
If that's the case, I still don't think a small spinning wheel should consume >=100% CPU, but that at least would mean it's not picocss specific - background blurred or not.
Describe the issue
Current Behavior
If I'm using
aria-busy=true
inside e.g. a div withindialog
-tags, my web browser's processing resources skyrocket.This does not happen if the
aria-busy=true
-animation is happening without the dialog involved.Expected Behavior
Such a basic animation like
aria-busy=true
should not use up all available CPU resources but run smoothly at no cost.Reproduction URL
https://codepen.io/mirko2342/pen/yLdoemy
Environment
Linux, Firefox and Chromium
The text was updated successfully, but these errors were encountered: