Repository navigation
Conversation
…he span renders directly over and outside of the disabled input
|
@coderabbitai full review |
✅ Action performedFull review finished. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: QUIET Plan: Advanced Run ID: 📒 Files selected for processing (21)
Included review availability: Your plan provides up to 10 included reviews per hour; 1 remains after this review. 📝 SummarySummary by CodeRabbit
WalkthroughStorybook stories now control component initialization around rendering, use explicit ChangesStorybook behavior updates
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~30 minutes Change: Bug fix · Severity of issue fixed: Medium Suggested labels: Merge Risk: ⚪ Minimal · up to Storybook initialization runs in supported browsers that provide requestAnimationFrame, so no actionable merge risk remains. 🚥 Pre-merge checks | ✅ 7 | ❌ 3❌ Failed checks (3 warnings)
✅ Passed checks (7 passed)
Full details: Out of Scope Changes checkExplanation
Full details: Regression Test Targets The ChangeExplanation The PR changes production behavior in Resolution Add or modify a Mocha spec under Full details: Accessibility Verification DeclaredExplanation The check applies because the PR adds the Resolution Document coverage for the changed input-mask behavior. Include assistive technology and browser combinations, such as NVDA with Firefox or Chrome, JAWS with Chrome or Edge, and VoiceOver with Safari. Record verification for native Comment |
Summary
Fixed remaining stories with enhanced components. The remaining stories not captured in #6664 have been updated to initialize the enhanced components on mount.
Breaking change
This is not a breaking change.
Related issue
Closes #6694
Related pull requests
This PR is for a branch off #6692.
I'm expecting that PR to be merged first, as some of these changes require those changes in order to be viewable.
Preview link
Not available
Problem statement
The USWDS Storybook app doesn't initialize a few enhanced components when the story renders.
Some of the consequences:
-- The banner and header submenu dropdown is expanded by default in each of the "PAGES" stories.
-- The date range picker with restricted dates stories don't apply the upper and lower bounds of the date range.
-- On small screens, the big footer variant is meant to render with the nav items collapsed into accordions, but instead they are expanded.
-- Input mask doesn't enforce any pattern.
-- Validation appears to work but dumps errors into the console.
All of these issues are resolved by initializing the appropriate enhanced components on mount.
Solution
The solution is to initialize the component with .on() on mount.
Major changes
Not applicable
Testing and review
Clone the repo, checkout this branch, execute npm install && npm start.
Manipulate and visually inspect the components affected by this PR.
Here are screenshots to show it's resolved:







Warnings here, but no errors:
Errors previously seen: