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

Custom Range component should still have an input #164

Open
idanen opened this issue Apr 13, 2020 · 1 comment
Open

Custom Range component should still have an input #164

idanen opened this issue Apr 13, 2020 · 1 comment

Comments

@idanen
Copy link

idanen commented Apr 13, 2020

When creating custom elements, we should not degrade the experience, so even for minimal implementation input[type=range] should be used to keep standard behavior as expected.

@elkarouani
Copy link
Contributor

I guess this needs an example so the issue can be more understandable !

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