[docs] Fix Field validity API descriptions#4592
Merged
atomiks merged 3 commits intomui:masterfrom Apr 14, 2026
Merged
Conversation
commit: |
Bundle size
PerformanceTotal duration: 1,265.35 ms ▼-174.45 ms(-12.1%) | Renders: 53 (+0) | Paint: 1,974.43 ms ▼-205.15 ms(-9.4%)
...and 7 more. View full report Check out the code infra dashboard for more information about this PR. |
✅ Deploy Preview for base-ui ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
986cabe to
a99695b
Compare
Contributor
|
All Field/Form components have this same wording at the moment |
eca885d to
4f657b2
Compare
atomiks
approved these changes
Apr 13, 2026
flaviendelangle
approved these changes
Apr 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I was having a quick look at #4365. This didn't read quite right; this seems like a typo. I can only think of two options here:
Judging from https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Selectors/:invalid, the former seems correct.