-
Notifications
You must be signed in to change notification settings - Fork 148
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
Update to USWDS 3.3.0 / Patterns / Report #1889
Conversation
Not necessary in a navigation element
- Remove mobile from when not to use, since we don't consider that universal guidance. Teams should not use our component on mobile, but a mobile in-page nav is not impossible
Removing all the intersection observer details, since these options are not available to the implementor. It's useful info, but there's nothing for teams to do with it
…ers to tab to in-page nav before main content
The original 3.0 release note was updated. Co-authored-by: Amy Leadem <93996430+amyleadem@users.noreply.github.com>
Based on PR comment #1871 (comment)
From suggestion in PR comment #1871 (comment)
Base on PR comment #1871 (comment). Co-authored-by: Amy Leadem <93996430+amyleadem@users.noreply.github.com>
…:uswds/uswds-site into mm-inclusive-patterns-in-page-navigation
Changed example for ethnicity
Update in-page nav with new properties
IDP component alert and combobox content updates
|
Links to USWDS 3.3.0 will fail until the release is published |
|
In a perfect world, on the Name form template the
|
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.
I think it looks really good @thisisdano . I would love to see the Name form template preferred name match the pattern's preferred name hint text but it's not a deal breaker.
This add a number of updates to the design system:
Preview →