You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in v11 when using Contained Tabs or Vertical Tabs an adopter must use a <Layer> inside if any field components are being used inside the TabPanel. TabPanel has no connection at the moment if the <Tab> is contained or not.
idea: Somehow TabPanel will know if it is a type of Contained Tab and automatically wrap the children in a <Layer>. We could also make a codemod that would remove any <Layer> components being used, so that it would be a seamless transisition for adopters
The text was updated successfully, but these errors were encountered:
#17215
^ follow up from this PR
Currently in v11 when using Contained Tabs or Vertical Tabs an adopter must use a
<Layer>
inside if any field components are being used inside theTabPanel
.TabPanel
has no connection at the moment if the<Tab>
iscontained
or not.idea: Somehow
TabPanel
will know if it is a type ofContained
Tab and automatically wrap the children in a<Layer>
. We could also make a codemod that would remove any<Layer>
components being used, so that it would be a seamless transisition for adoptersThe text was updated successfully, but these errors were encountered: