-
-
Notifications
You must be signed in to change notification settings - Fork 298
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
High CPU usage when using variant-form-material
in a each
statement
#1805
Comments
@djdembeck the Material styled variants are handled with CSS, per: That's it, that's all that occurs when you implement those classes - some additional styles are added. The only style that might have an affect on performance would be So I'd recommend the following:
|
Thanks for the quick response!
You were correct, removing only It may be worth mentioning as well, this seems to be a Blink (Vivaldi/Chrome) engine issue. I tested on Firefox, and with |
Thank you for confirming @djdembeck, then the role of this ticket will be to remove that in an upcoming patch. Yeah browser each have their own ways to go about this. It may be they lean on the CPU more than the GPU for this effect in particular. Hopefully that changes in the future. The latter would likely be more performant when a good GPU is present! |
Current Behavior
In a table-based form of repeated rows of inputs, all 3 columns use
class="input variant-form-material"
. When the form is loaded, there is a visual issue on the page, the browser slows down, and my CPU meter goes to 100%. If I removevariant-form-material
only, the CPU usage goes back to normal on that page.Expected Behavior
Using
variant-form-material
on a repeated input form, should have no affect on performance, compared to standard styling.Steps To Reproduce
structure for each td. In my test case, I am using this in a table with 35 items (on an edit form), within a Stepper component.
3. Load the form page, specifically a form that contains data for the 35
td
elements.4. Notice CPU spike.
Link to Reproduction / Stackblitz
No response
More Information
No response
The text was updated successfully, but these errors were encountered: