Consider having a touch screen where one tries to do a scroll of a component containing ngx-slider. If the scroll touch gesture is started on the ngx-slider bar the value of the ngx-slider is changed to where the touch occurred. One might want the value not to be changed.
Solution
This allows parent component containing ngx-slider to issue an event informing the ngx-slider to basically not take an action upon this touch event. I.e. the parent decides whether touch event belongs to ngx-slider or not.
Limitations / Future work
The handle movement is started and after the cancel event it moves back to the original position. Some other solution that would prevent such a "glitch" completely could be nice.
Issue
Consider having a touch screen where one tries to do a scroll of a component containing ngx-slider. If the scroll touch gesture is started on the ngx-slider bar the value of the ngx-slider is changed to where the touch occurred. One might want the value not to be changed.
Solution
This allows parent component containing ngx-slider to issue an event informing the ngx-slider to basically not take an action upon this touch event. I.e. the parent decides whether touch event belongs to ngx-slider or not.
Limitations / Future work
The handle movement is started and after the cancel event it moves back to the original position. Some other solution that would prevent such a "glitch" completely could be nice.
Closes #139