Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
fix: Properly clear Autocomplete wrapped SearchField when "x" button is pressed #7606
fix: Properly clear Autocomplete wrapped SearchField when "x" button is pressed #7606
Changes from 1 commit
eaf75e6
632f2ab
397b99f
f79ad17
d4ea169
8f42edb
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
A bit non-standard to have both
inputProps
andtextFieldProps
(at least I don't think we have something like this in other hooks), but some props should be passed to the hooks (onKeyDown, onChange, value) so that SearchField's clear button works properly and the controlled input value is synced between this hook and useSearchField. Other stuff likearia-controls
needs to go directly on theinput
and aren't regarded as valid props inAriaTextFieldProps
hence the split. I could expand AriaTextFieldProps to accepts those attributes instead if want to go that directionThere 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.
Wouldn't SearchField/TextField's Contexts interfere with InputProps anyways? so really there are three components we're potentially targeting, two of them just happen to use the same set of props?
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.
hmm maybe we should add those props to AriaTextfieldProps. Then we could remove the weird merging with InputContext too. Looks like just
aria-controls
,autoCorrect
, andspellCheck
are missing? Those seem like reasonable props for TextField to support.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.
Is this still needed?
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.
shouldn't need the spread?