Skip to content

Conversation

chirokas
Copy link
Contributor

Closes #8995

The Chrome bug has been fixed, so this workaround can be removed. It also caused a TextArea reset issue.
https://issues.chromium.org/issues/333940413

✅ 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:

@chirokas chirokas marked this pull request as ready for review October 10, 2025 15:17
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.

Our usual stance is last 2 major releases are supported. So I'm ok with this PR.

However, I will note that the bug was fixed in a release from only a year ago https://www.gitclear.com/open_repos/chromium/chromium/release/130.0.6679.0

I don't know if that gives anyone else pause on the team given the difference between timelines on majors of browsers like Chrome vs Safari.

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.

TextArea resets to its defaultValue after submitting useActionState

2 participants