-
Notifications
You must be signed in to change notification settings - Fork 32
feat(Tabs): add shouldForceMount prop to TabPanel #3214
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
Conversation
|
View your CI Pipeline Execution ↗ for commit f0ca425 ☁️ Nx Cloud last updated this comment at |
dreamwasp
left a comment
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.
tested w/ and w/o VO + looks great
|
|
||
| By default, when a tab is not selected, the `TabPanel` is not mounted in the DOM. This is to improve performance and avoid unnecessary rendering. However, if you need to force mount the `TabPanel` even when it is not selected, you can pass the `shouldForceMount` prop to the `TabPanel` component. | ||
|
|
||
| The `shouldForceMount` prop is a wrapper around the `shouldForceMount` prop in react-aria-components that also visually hides the inactive tab panel. |
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.
maybe link to the react-aria-components docs here>
|
📬 Published Alpha Packages: |
|
🚀 Styleguide deploy preview ready! Preview URL: https://69307dd7a48c0805595486d5--gamut-preview.netlify.app |
Overview
Adds
shouldForceMountprop toTabPanelto render theTabPanelin the DOM and hide it visually. This is a request from the Author team to match functionality from reach/tabs that was removed when we migrated over to react-aria-components tabs.PR Checklist
Testing Instructions
PR Links and Envs