-
Notifications
You must be signed in to change notification settings - Fork 0
finished inputs #8
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
base: main
Are you sure you want to change the base?
Conversation
Thanks for contributing! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
trying it out, it looks good
I think we should allow passing through more HTML props on <input>
(see below), plus a few nitpicks
When it shows a hint, I can't click on the text itself to edit it. Maybe pointer-events: none
it?
Though that said, on mobile there's currently no way to accept the hint. Maybe tapping on the hint should accept it, while tapping anywhere else goes through to the input. Apparently a child element can override a parent's pointer-events: none
so maybe this isn't too difficult to do
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
} | ||
|
||
return ( | ||
<div className={`dropdown-wrapper ${theme} ${size}`}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should probably also have a <select>
element so that you can tab focus on it, mostly for accessibility, but on keyboard you can also type the first few letters to select an option
pull request for inputs, making dropdowns in a separate branch