Skip to content

fix: Allow selectedKey=null to clear value in HiddenSelect #8330

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

Merged
merged 2 commits into from
Jun 21, 2025

Conversation

chirokas
Copy link
Contributor

@chirokas chirokas commented Jun 1, 2025

Closes #8032

let onChange = useEffectEvent(() => {
state.commitValidation();
});

runs before
onChange: (e: React.ChangeEvent<HTMLSelectElement>) => state.setSelectedKey(e.target.value)

, which leads to the autofill failing.

See here for more information

✅ Pull Request Checklist:

  • Included link to corresponding React Spectrum GitHub Issue.
  • Added/updated unit tests and storybook for this change (for new code or code which already has tests).
  • Filled out test instructions.
  • Updated documentation (if it already exists for this component).
  • Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

Copy link
Member

@snowystinger snowystinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Appears to leave behaviour for autofill intact for Dashlane. @yihuiliao can you check with chrome's autofill?
Verified it allows the hidden input to be reset to null as expected

@@ -1715,6 +1715,7 @@ describe('Picker', function () {
expect(options.length).toBe(60);
options.forEach((option, index) => index > 0 && expect(option).toHaveTextContent(states[index - 1].name));

fireEvent.input(hiddenSelect, {target: {value: 'CA'}});
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just double checking, is this just testing that onSelectionChange isn't called twice? asking because it seems it was passing before the changes in HIddenSelect

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah

@@ -99,8 +102,9 @@ export function useHiddenSelect<T>(props: AriaHiddenSelectOptions, state: Select
disabled: isDisabled,
required: validationBehavior === 'native' && isRequired,
name,
value: state.selectedKey ?? undefined,
onChange: (e: React.ChangeEvent<HTMLSelectElement>) => state.setSelectedKey(e.target.value)
value: state.selectedKey ?? '',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was changed previously in #7670 to fix a different issue. @snowystinger do you remember what was going on there?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, that was to fix the autocomplete. If I recall correctly, it viewed the '' as a controlled value for the field and wouldn't autofill as a result, React would just overwrite it with the empty string again as there was no onChange event. There is apparently an onInput change for it though, so we can use that to update with the value for auto fill.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, I missed the onInput. Does having both cause setSelectedKey to run twice then?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good question, i doubt any of our tests check that, so will need to verify

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh looks like the added test covers it.

@devongovett devongovett added this pull request to the merge queue Jun 21, 2025
Merged via the queue into adobe:main with commit da50cd0 Jun 21, 2025
29 checks passed
@chirokas chirokas deleted the select-null-selectedKey branch June 21, 2025 06:32
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

Successfully merging this pull request may close these issues.

Controlled react-aria-components Select cannot be nulled
3 participants