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 was archived by the owner on Mar 5, 2023. It is now read-only.
getBoundingClientRect() is really expensive to call on every mousemove. i think caching it and simply incrementing the x/y offsets by the mouse position should be possible while the overlay is within bounds. a custom invalidation function can be added to support cases when the overlay content changes and needs to re-measured.
getBoundingClientRect() is really expensive to call on every mousemove. i think caching it and simply incrementing the x/y offsets by the mouse position should be possible while the overlay is within bounds. a custom invalidation function can be added to support cases when the overlay content changes and needs to re-measured.
thoughts? cc @tobyzerner