material-components / material-components/material-components-android
[Slider] Stop indicators don't fulfil their purpose when the slider has too many acceptable values
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17.4k
- Forks
- 3.2k
- PR merge metrics
- No merged PRs in 30d
Description
**Actual behavior:**
https://github.com/user-attachments/assets/ceb05660-dd98-4218-8c9e-06fabcb47b2b
**Expected behavior:** [link](https://m3.material.io/components/sliders/guidelines#3da6e500-63d9-4a57-b00d-d2c01415ea7a)
> On discrete sliders, stop indicators show the predetermined values that can be chosen along the track. The slider snaps to the closest stop.
**Material Library version:** 1.13.0-alpha04
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing the slider behavior described in the issue on Material Library 1.13.0-alpha04, then compare it with the linked Material Design guideline for discrete sliders. Done means stop indicators remain useful and the slider snaps to the closest predetermined value when many values are available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- design, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100