Hacker News new | ask | show | jobs
by Rygian 556 days ago
> The "native" part is somewhat open for discussion. I call it native because the library uses two native HTML range inputs. This means that all of the native interactions and accessibility features are preserved.

My dividing line is: if it needs Javascript to work as intended, it's not native anymore.
2 comments
onli 556 days ago
I agree. And I think that's the common usage?

I still get what the author is aiming at though, using combined regular sliders instead of implementing a div soup animated by js moved this a lot closer to a native solution. Probably closest it can be, if the javascript can't be replaced by clever css.

It's still a very useful widget to have available, and that space was missing implementations. Native or not.

link
extra88 556 days ago
Usually but it's not entirely clear cut. The <dialog> element is native but you have to use JavaScript to open it in the modal state. Before the popover attribute, you couldn't open it at all without JavaScript.

There are also native, vanilla JavaScript methods for things like form validation that I would consider distinct from a library that doesn't use the browser's internal validation tooling at all.

link