(As gently as I can muster while suppressing a mischievous grin...
That "slider" can't be broken because it's not real. It's an abstracted virtual simulation of a real sliding trim potentiometer. The abstraction is designed to provide the user with just enough sense of a real appearance so as to make the functionality connection with a real potentiometer easily apparent. That in turn leverages the user's prior knowledge so no new training is required to immediately put the simulation to use.
Further, the implementation of that slider abstraction already knows about the user's penchant for emotionally slamming real sliders too far in frustrated attempts to get more of what they think it is they want in post-processing.
So design envelope boundaries have been established and also implemented in code beyond the user's control to preempt this behavior. The user can continue pushing his mouse off the desk and out the window onto the pavement below, and that little simulated slider will continue to stop at its upper limit without "breaking" every single time.
You see, the key to a successful software simulation is to assert extremely tight control over the user to keep him firmly within the applicable abstract design envelope, while at the same time making him believe that he has full and complete control over his actions. But he doesn't. He can't be trusted to...
It's very much analogous to pacifying a petulant child after saying no by offering up three new options for him to choose between, all of which have already been pre-vetted by you as being acceptable. Implement that correctly and the child feels vindicated because he really did get his way in the end by making his own final choice.)
:
Ken