Updates FormControl validation example to better align with the interface guidelines
I added a more dynamic validation example that conforms to the form validation patterns defined in the form interface guidelines.
⚠️ No Changeset found
Latest commit: 72cffd701d7245e5b5a46a8ed010866a1e86d9f9
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
size-limit report 📦
| Path | Size |
|---|---|
| dist/browser.esm.js | 88.82 KB (0%) |
| dist/browser.umd.js | 89.43 KB (0%) |
Hi! This pull request has been marked as stale because it has been open with no activity for 60 days. You can comment on the pull request or remove the stale label to keep it open. If you do nothing, this pull request will be closed in 7 days.
👋🏻 @mperrotti would you still like reviews on this? Happy to get a buddy assigned if you don't want this to go stale.
@lesliecdubs - I completely forgot about this 😅
We decided to put this example into the stories instead of the docs site. I just got distracted by other work and haven't come back to it yet.
I'll update today and mark as "Ready for review".
I made the update, but after talking to @ericwbailey, I'm uncertain that we'll stick with the guidance that this change is demonstrating:
If an interactive summary of errors is not shown, the first invalid input should be focused and scrolled into the viewport
I'll be bringing it to next week's a11y design office hours. Then I'll either mark this PR as "Ready for review" or close it.
When I brought this to a11y office hours, we decided to stick with the existing guidance. I will come back to this later this week or early next week.
Hi! This pull request has been marked as stale because it has been open with no activity for 60 days. You can comment on the pull request or remove the stale label to keep it open. If you do nothing, this pull request will be closed in 7 days.