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
Some Waltz callback is taking 110ms per keystroke when composing a tweet. Most of us can press keys faster than that and it is really annoying. Just go to Twitter and compose a tweet.
Here is the flame chart:
Do you really need to capture every keystroke when we are not even on the login page?
The text was updated successfully, but these errors were encountered:
Some Waltz callback is taking 110ms per keystroke when composing a tweet. Most of us can press keys faster than that and it is really annoying. Just go to Twitter and compose a tweet.
Here is the flame chart:

Do you really need to capture every keystroke when we are not even on the login page?
The text was updated successfully, but these errors were encountered: