Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

<mat-slider> disable value change on click rage line #15526

Closed
webdevlapani opened this issue Mar 19, 2019 · 7 comments
Closed

<mat-slider> disable value change on click rage line #15526

webdevlapani opened this issue Mar 19, 2019 · 7 comments
Labels
area: material/slider feature This issue represents a new feature or feature request rather than a bug or bug fix needs: discussion Further discussion with the team is needed before proceeding P5 The team acknowledges the request but does not plan to address it, it remains open for discussion

Comments

@webdevlapani
Copy link

Please describe the feature you would like to request.

  • we need to one property using this we can control the range value change or not on click or touch on <mat-slider> line.

What is the use-case or motivation for this proposal?

I use material angular in my website its work good but when I use in a mobile device I face a problem like when I scroll down that time I touch by mistake on mat range slider reason for that my rage was change if I not want

So I want a solution for that like I need only mat-slider value will change when user drag handle of mat-slider instead of clicking slider.

Is there anything else we should know?

https://stackoverflow.com/questions/55205407/mat-slider-touch-issue-in-mobile-device

@Domvel
Copy link

Domvel commented Mar 20, 2019

The change event is fired twice. See #14363 It's a bug.
If you click on the "range line" the event should also be fired only once. Only on pointer (mouse / touch) up. But your request to disable click on range-line is good. In other words: Only allow slider-thumb interaction.

@webdevlapani
Copy link
Author

webdevlapani commented Mar 24, 2019

The change event is fired twice. See #14363 It's a bug.
If you click on the "range line" the event should also be fired only once. Only on pointer (mouse / touch) up. But your request to disable click on range-line is good. In other words: Only allow slider-thumb interaction.

Yes, that's really good.

@jelbourn jelbourn added feature This issue represents a new feature or feature request rather than a bug or bug fix P5 The team acknowledges the request but does not plan to address it, it remains open for discussion discussion labels Mar 25, 2019
@webdevlapani
Copy link
Author

@jelbourn This is important for the community because in the mobile device when we scroll that time changed the value of the range slider if we don't want

@igornes
Copy link

igornes commented Sep 29, 2019

Agree that this is an important request. We have the same issue with phone interactions. Users set the value of the slider by mistake while swiping vertically to scroll the form.

@mmalerba mmalerba added needs: discussion Further discussion with the team is needed before proceeding and removed discussion labels Mar 3, 2020
@BrianMikinski
Copy link

Any idea of a work around or if the Angular team will give us an API to do accomplish this?

@jelbourn
Copy link
Member

jelbourn commented Aug 5, 2021

Duplicate of #4711

@jelbourn jelbourn marked this as a duplicate of #4711 Aug 5, 2021
@jelbourn jelbourn closed this as completed Aug 5, 2021
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: material/slider feature This issue represents a new feature or feature request rather than a bug or bug fix needs: discussion Further discussion with the team is needed before proceeding P5 The team acknowledges the request but does not plan to address it, it remains open for discussion
Projects
None yet
Development

No branches or pull requests

7 participants