fix(material/slider): make valueChange emit only on change and not on…

[wagnermaciel]

… input

Fixes #26496

[mmalerba]

Is there a bug associated with this?

[wagnermaciel]

Yes - #26496

[angelaki]

Since the new behavior is just different and not wrong, maybe it would be nice to switch the behavior (keeping the old one as default)? If interessnted, I'd adopt the PR regardingly.

[wagnermaciel]

@angelaki Technically the new behavior is wrong. The valueChange event should only emit on value change which is different from on input

[angelaki]

@wagnermaciel Ah, I see! If I'm interessted in all the intermediate values I should listen to onInput? But where to find this event? It doesn't seam to be part of the documentation (https://material.angular.io/components/slider/api). Thank you for clarification.

[wagnermaciel]

@angelaki Hey, yep you're right. With the latest implementation of the slider, the native browser inputs are exposed, which means you can just listen to input events directly on it as if it was an <input type="range" />.

I believe the syntax should be something like this:

<mat-slider>
    <input matSliderThumb (input)="handleInput($event)">
</mat-slider>

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}