Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

>=100% CPU load if aria-busy=true animation in dialog #592

Open
mirko opened this issue Aug 10, 2024 · 3 comments
Open

>=100% CPU load if aria-busy=true animation in dialog #592

mirko opened this issue Aug 10, 2024 · 3 comments

Comments

@mirko
Copy link

mirko commented Aug 10, 2024

Describe the issue

Current Behavior

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.

Reproduction URL

https://codepen.io/mirko2342/pen/yLdoemy

Environment

Linux, Firefox and Chromium

@mirko mirko changed the title >=100% CPU load if aria=true animation in dialog >=100% CPU load if aria-busy=true animation in dialog Aug 11, 2024
@dev-willis
Copy link

Yeah, I couldn't reproduce it either.

@mirko
Copy link
Author

mirko commented Aug 17, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@mirko @dev-willis and others