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
While the CSS renderer could check if the separate style changes really caused changes and only update those styles, setting the cssText directly always rewrites the styles. Since the render updates are going constantly due to the infinite loop, this makes development really hard because in the development console, while you'd try to change a style property it already renders the next frame.
Maybe it even causes performance issues but I didn't test it.
I downloaded the code and restored the state to before the update in my project and it works fine now.
The text was updated successfully, but these errors were encountered:
Same issue here.
CSS is refreshing continuously so I can't inspect element styles.
You can confirm whether it is refreshing in the CSS computed tab. In the computed tab, you can see nothing.
The v2.0.5 refactoring, while making the code somewhat cleaner, also introduced an issue with the rendering.
See the diff here: 1e302a8#diff-82e2514055cb74ebb7ad8048a1e13c101ca9276fe11790f259e165ac6eadd528
While the CSS renderer could check if the separate style changes really caused changes and only update those styles, setting the cssText directly always rewrites the styles. Since the render updates are going constantly due to the infinite loop, this makes development really hard because in the development console, while you'd try to change a style property it already renders the next frame.
Maybe it even causes performance issues but I didn't test it.
I downloaded the code and restored the state to before the update in my project and it works fine now.
The text was updated successfully, but these errors were encountered: