I understand what you mean. However, as I said in #78, this change will probably break existing apps (like if someone is using rz-slider-step="{{ step }}").

Moreover, when changing the step with your solution, a NaN appears briefly above the slider so I think you are missing something... self.resetSlider(); maybe?

I think if we do this, we should do the same for the rz-slider-precision and other attrs using @ bindings to be more consistent... Then it would mean we bump to a breaking change release so 0.2.0.

If you don't want to break existing implementations why don't you introduce a new 'rz-slider-nonStaticStep' or something? I need this feature so you have my vote :) 👍

Hmmm I'm not really fan of this solution because I already think that there are too many attributes on this directive.... I'm even considering using a rz-slider-options that would use an object containing all the non-mandatory fields and only keep rz-slider-model and rz-slider-high. Then all the options would be updatable at runtime.

What do you think of this solution? This would definitively be a 2.0 release.

Sounds good 👍

Stupid question... Why does this dynamic step change works?
https://jsfiddle.net/zfee1pxb/3/
https://jsfiddle.net/zfee1pxb/4/

There is no watch on step alone but since you modify other properties that are watched (model for instance), the slider is refreshed and so the step is updated.

OK and here https://jsfiddle.net/zfee1pxb/5/ the update is triggered when moving the bubble right? So the only thing that does not work yet is that the bubble does not jump around when changing the step right?

Not only because if you show the ticks on the slider, then they are not updated either:
https://jsfiddle.net/pom92p9r/

I have started to implement what I mentioned above about rzSliderOptions:
https://github.com/rzajac/angularjs-slider/blob/2.0.0/src/rzslider.js#L34 .
What do you think?

It looks like mentioned :)

Please see #158