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
I am still investigating whether or not my code caused this, but it seems that there is never a check to prevent node from being null
var node = _this.slider;
var coordinateStyle = constants.orientation[orientation].coordinate;
var directionStyle = reverse ? constants.orientation[orientation].reverseDirection : constants.orientation[orientation].direction;
var clientCoordinateStyle = 'client' + (0, _utils.capitalize)(coordinateStyle);
var coordinate = !e.touches ? e[clientCoordinateStyle] : e.touches[0][clientCoordinateStyle];
var direction = node.getBoundingClientRect()[directionStyle];
Is this expected behavior from rangeslider?
I have successfully recreated my error, as it only happens when my react component disappears (because it gets turned off and gets replaced). Is there a way I can prevent this error from happening?
The text was updated successfully, but these errors were encountered:
Per Darthzeran's observation, I tried adding a check and it indeed fixed the error for me.
Starting around line 194 in the _this.position function:
` if(_this.slider) {
var node = _this.slider;
var coordinateStyle = constants.orientation[orientation].coordinate;
var directionStyle = reverse ? constants.orientation[orientation].reverseDirection : constants.orientation[orientation].direction;
var clientCoordinateStyle = 'client' + (0, _utils.capitalize)(coordinateStyle);
var coordinate = !e.touches ? e[clientCoordinateStyle] : e.touches[0][clientCoordinateStyle];
var direction = node.getBoundingClientRect()[directionStyle];
var pos = reverse ? direction - coordinate - grab : coordinate - direction - grab;
var value = _this.getValueFromPosition(pos);
return value;
}`
I am still investigating whether or not my code caused this, but it seems that there is never a check to prevent node from being null
Is this expected behavior from rangeslider?
I have successfully recreated my error, as it only happens when my react component disappears (because it gets turned off and gets replaced). Is there a way I can prevent this error from happening?
The text was updated successfully, but these errors were encountered: