Thanks for creating a composite slider solution. It generally works well, but I've had to work around a couple issues:
min/max attributes assigned to scope variables that are later changed don't actually result in changes to the slider limits as you stated it should.
because of ♯1, I cannot use the slider element with ng-show, as I don't want to initially display the range slider and don't have the min/max values until I want to show the slider.
because of ♯2, I resorted to using ng-if, which evaluates to true at the same time I determine the appropriate min/max and initial from/to values. However, as ng-if creates a child scope, I had to use $parent in the <section ng-model> (but I don't have to in the <label>--see below).
I would like to use ng-show and dynamically update min/max values, but if I choose ng-if, ng-model should reference the variable in the parent scope like other elements.
Thanks for creating a composite slider solution. It generally works well, but I've had to work around a couple issues:
min
/max
attributes assigned to scope variables that are later changed don't actually result in changes to the slider limits as you stated it should.ng-show
, as I don't want to initially display the range slider and don't have the min/max values until I want to show the slider.ng-if
, which evaluates to true at the same time I determine the appropriate min/max and initial from/to values. However, asng-if
creates a child scope, I had to use$parent
in the<section ng-model>
(but I don't have to in the<label>
--see below).I would like to use
ng-show
and dynamically update min/max values, but if I chooseng-if
,ng-model
should reference the variable in the parent scope like other elements.