[Visual Request] Suggestions for improving default slider styling in dash=4.0.0
@KoolADE85 ya está trabajando en esto.
Desde el 20/2/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Hi!
First off, thank you for the great work on the redesigned Dash components - they look great overall! 🥳
While using the updated sliders, I noticed a few small visual details that might be worth reconsidering in the default styling. None of these are major issues, and we've been able to address them with custom CSS on our end, but I wanted to share the feedback in case it's helpful :)
- Here is the example app with the environment: https://py.cafe/huong-li-nguyen/dash-slider
- Using dash=4.0.0
1. Slider track and dot opacity
The current opacity applied to the slider track and dots makes them feel slightly visually disconnected. Removing the opacity (or assigning a different color) might help the elements feel more cohesive as a single component.
In our case, we worked around this by overriding the Dash CSS variable with a different color. However, it might be worth considering whether the default styling could achieve this more naturally.
2. Dot alignment
The slider dots don’t appear to be perfectly center-aligned with the track when using dots=True- they look slightly offset on close inspection (see screenshot). We corrected this with custom CSS, but it may be worth adjusting in the default styles to ensure precise alignment.
3. Start and end dot positioning
This one is more subjective, but it might look cleaner if the first and last dots were positioned exactly at the start and end of the track, rather than slightly inset.
Here the start and end point are positioned right at the edge of the track:
Currently the start/end dot are positioned slightly inset:
Would any of these adjustments be feasible in the default styling?
Thanks again for all your work on this - we really appreciate the improvements! 🫶
Best,
Li
- Lenguaje dominante
- Python
- Estrellas
- 24.4k
- Forks
- 2.3k
- Merge medio
- 1 d 21 h
- PR fusionados (30 d)
- 19
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de plotly/dash
-
good first issue P3 size: 1 task
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
enhancement P2 size: 5
Dificultad 5/5 Más de una semana Aptitud para principiantes 45/100
-
enhancement P3 size: 10+
-
P2 size: 1 task
-
enhancement P3 size: 1
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
Todos los issues de plotly/dash
Issues similares
-
essnmx good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
-
[Feature] 奇物选择添加优先级 Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
syfoud/Simulated_Scepter#174 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Giskard-AI/giskard-oss#2840 · 1 comentario ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Abiertoarea: repo bug perceived difficulty: 2
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
yeti-platform/yeti#1380 ·