reach/reach-ui

Native range input vs Slider component

Francesco-Lanciana opened this issue · 1 comments

❓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?

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.