Replies: 1 comment 2 replies
-
|
I suspect the recent changes/tidying up of containers has thrown off CSS = """
TabbedContent ContentSwitcher {
border: solid red;
}
"""doing something like the following, for the purposes of your example code, should improve things for now: CSS = """
TabbedContent ContentSwitcher {
height: 1fr;
}
"""Likely set the height to whatever makes sense for your app. I'll raise an issue to remind us to revisit this and review the most appropriate parent class for the various parts. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This is a followup on issue #2385.
I currently use
Tabsfor the tab bar andContentSwitcherto switch between content views. This works fine in 0.20.1 and 0.22.0. I am trying now to move toTabbedContentandTabPaneinstead.The content shown for the tabs is usually a
Verticalcontainer with a complex sub-structure. WithTabPaneI have the problem that using aVerticalcontainer (or any container class) as a child the result seems unpredictable missing children from theVerticalcontainer.I tried to isolate the problem but found more cases where there are problems (using version 0.22.0):
The output for the different tabs looks like this:
I am a bit confused by the the different results. What am I doing wrong?
Beta Was this translation helpful? Give feedback.
All reactions