Repository navigation
Inserting a TabBarSelection doesn't cause its descendants to rebuild #1017
Description
Dynamically adding a TabBarSelection ancestor of a TabBar or a TabBarView will not cause the descendants to be rebuilt, which means that the TabBar and TabBarView will not automatically begin listening to the the TabBarSelection's performance. The problem generalizes to any TabBarSelection descendant that uses TabBarSelectionState.registerPerformanceListeners() to track the selection's performance.
It's not clear how to handle this. Does TabBarSelection need to walk its subtree and rebuild nodes that implement some "I am going to register performance listeners" marking interface?
See also: #1007
Activity
Hixie commentedon Dec 25, 2015
One option might be to have the selection announce its existence on initState.
Hixie commentedon Jun 27, 2017
cc @HansMuller Is this even still relevant? I'm going to close this since we don't have a TabBarSelection anymore, but if this still makes sense in some way please reopen it.
github-actions commentedon Aug 16, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.