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
I suspect there are a few issues here (or rather a few operations that might suffer from a similar problem) but I think this example perfectly illustrates the confusion that could arise. Consider the following code:
There is a Tabs within a TabPane within TabbedContent. There is a Button that, when pressed, will disable the first Tab of the Tabs that the developer has added. When pressed, you would expect the Tab with the title One to grey out and become unusable.
Instead what happens is every tab becomes disabled, as does the Button too:
This will, of course, be due to the message leaking up to the TabbedContent and its first tab getting disabled due to it having a similar ID.
Compare what happens with this code, where I give the TabPane an ID that avoids the clash.
I suspect there are a few issues here (or rather a few operations that might suffer from a similar problem) but I think this example perfectly illustrates the confusion that could arise. Consider the following code:
There is a
Tabs
within aTabPane
withinTabbedContent
. There is aButton
that, when pressed, will disable the firstTab
of theTabs
that the developer has added. When pressed, you would expect theTab
with the titleOne
to grey out and become unusable.Instead what happens is every tab becomes disabled, as does the
Button
too:This will, of course, be due to the message leaking up to the
TabbedContent
and its first tab getting disabled due to it having a similar ID.Compare what happens with this code, where I give the
TabPane
an ID that avoids the clash.It feels like something should be done to isolate the
TabbedContent
from anyTabs
that might be in one or more of its panes.The text was updated successfully, but these errors were encountered: