-
Notifications
You must be signed in to change notification settings - Fork 106
feat(search-input): pf-search-input element #2899
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
Conversation
🦋 Changeset detectedLatest commit: 27c9694 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for patternfly-elements ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
adamjohnson
left a comment
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.
Some considerations to ponder:
- Right now this is feeling more like a
<select>instead of<input type="search">. What actions can we take to make it feel more search like?- eg: adding submit button for search, form element inclusion, click to submit query...
- With Chromium leading the way with customizable selects, should this element try to utilize that API and wait to merge until that feature is stable?
- Have you considered trying to build on top of the
<datalist>element? Would the features coming to customizable selects help the case to use a<datalist>element?
I have to hand it to you Arathy: you go for the most complex components straight out of the gate! 😅
What I did
Developed the

pf-search-inputcomponent by leveraging thepf-selectautocomplete variant to enhance the search functionality and improve user experience.Testing Instructions