How about if the component only updates the range value after the “onmouseup” event has fired on the element, that should mean the socket can update the value but not trigger any events.
I was afraid that it won’t work on mobile, but actually tapping on mobile fires “mouseup” event so it works fine (at least on latest chrome).
Thanks.
I think it’s a common scenario to control input from few sources (by user interaction and remotely), so I thought it’s already solved in some nice manner.