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
Please see this git-repo for more info. (It also contains the code for the playground used in the video below)
Here's a video showcasing the performance difference between using bind:clientWidth and not using it:
Screen.Recording.2023-03-14.at.19.49.11.mov
Describe the proposed solution
MutationObserver? I know this is probably a difficult thing to refactor, but i just want to address this issue as it has been a big bottleneck for our software in some cases.
It's such a nice feature, but it's not stated anywhere that bind:clientWidth (or any of the other width/height bindings) will introduce a noticeably amount of performance overhead.
Alternatives considered
Every case has a different work-around
Importance
would make my life easier
The text was updated successfully, but these errors were encountered:
Describe the problem
Please see this git-repo for more info. (It also contains the code for the playground used in the video below)
Here's a video showcasing the performance difference between using bind:clientWidth and not using it:
Screen.Recording.2023-03-14.at.19.49.11.mov
Describe the proposed solution
MutationObserver
? I know this is probably a difficult thing to refactor, but i just want to address this issue as it has been a big bottleneck for our software in some cases.It's such a nice feature, but it's not stated anywhere that
bind:clientWidth
(or any of the other width/height bindings) will introduce a noticeably amount of performance overhead.Alternatives considered
Every case has a different work-around
Importance
would make my life easier
The text was updated successfully, but these errors were encountered: