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
{{ message }}
This repository has been archived by the owner on Nov 10, 2020. It is now read-only.
Event handlers should not trigger or slow down the main thread when they are not in use
Actual Behavior
## Steps to reproduce the behavior
Currently, support for passive only exists in native implementations of JS, so all of our D3 event handlers would need to be changed to work with the JS web API
Can i use shows that only some browsers support passive event handlers, the important caveats here being that:
chrome and firefox support passive event listeners.
'passive: true' will be most effective in desktop views where the screen will be resized more frequently. Although passive event handlers don't directly help optimize resize events, these events push the limit of the main thread, and force the user closer to the threshold where they experience lag. Any optimization here is beneficial.
If a browser doesn't support passive event listeners, it will be the same as it is now. We will ONLY see performance improvements
Expected Behavior
Event handlers should not trigger or slow down the main thread when they are not in use
Actual Behavior
## Steps to reproduce the behavior
Currently, support for passive only exists in native implementations of JS, so all of our D3 event handlers would need to be changed to work with the JS web API
Can i use shows that only some browsers support passive event handlers, the important caveats here being that:
Resources:
The text was updated successfully, but these errors were encountered: