I guess this is because the input and the slider are synchronized on key press.
I think this is counter intuitive and it should not have a strict validation on the value, but only for the movement on the slider. If the user edits the value through the input, the slider should reflect that value, but when the user moves the slider, it should move in step increments.
Same issue
As soon as another value is entered in the input, the slider renders my Chrome 40.0 Unresponsive by spiking CPU usage to around 25% before dying.
If I use a
paper-slider
element with both editable and specifying the step attribute, I can't use the input field to introduce a value.I guess this is because the input and the slider are synchronized on key press.
I think this is counter intuitive and it should not have a strict validation on the value, but only for the movement on the slider. If the user edits the value through the input, the slider should reflect that value, but when the user moves the slider, it should move in
step
increments.