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
h-split and v-split rely on offsetLeft and offsetTop, but these properties are calculated relative to the offsetParent, which is a closes positioned element. And the splits also use clientX and clientY, which are calculated within the viewport.
So, if the viewport does not coincide with the closest positioned element, a split's handler will jump on the first mouse move.
The text was updated successfully, but these errors were encountered:
I have been able to reproduce this issue and fix it. I have changed the position calculation to be determined by using pageXOffset, pageYOffset and getBoundingClientRect which fix the issue. Thank you for spotting this.
h-split
andv-split
rely onoffsetLeft
andoffsetTop
, but these properties are calculated relative to theoffsetParent
, which is a closes positioned element. And the splits also useclientX
andclientY
, which are calculated within the viewport.So, if the viewport does not coincide with the closest positioned element, a split's handler will jump on the first mouse move.
The text was updated successfully, but these errors were encountered: