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

Native range input vs Slider component #927

Open
Francesco-Lanciana opened this issue May 25, 2022 · 1 comment
Open

Native range input vs Slider component #927

Francesco-Lanciana opened this issue May 25, 2022 · 1 comment

Comments

@Francesco-Lanciana
Copy link

❓Question

Are there any advantages to using Reach UIs Slider component vs directly using a native range input? It seems like native range inputs handle most of what the Slider component can do, they are just a little finicky to style consistently across browsers. Is there something else I'm missing?

@bestow-jd
Copy link

One improvement I can say that the ReachUI slider has over the native range input is that the native range input generally sucks for mobile users. Out of the box it doesn't play nice with the mobile browser scrolling, it shows an odd "focus" box over the entire thing on tap, and dragging only works when you explicitly grab the thumb which is quite the frustrating experience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants