Replies: 2 comments 3 replies
-
|
That's because we prioritize zero-configuration higher than optimization. CSS transform can be faster in some situation. However it create a new stacking context which changes the behavior of overflowed element (ex. bvaughn/react-virtualized#122). So we don't use it, at least as default. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hmm, didn't know about that. Is there a way to switch to using transform, or do I need to create my own component wrapper for the core package? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
It's generally more performant to use
transform, because it can be GPU accelerated and avoids layout recalculations.Beta Was this translation helpful? Give feedback.
All reactions