Move TabBarView (and friends) to flutter/widgets.dart #175592

Activity

1. tirth-patel-nc

   added

   in triagePresently being triaged by the triage teamPresently being triaged by the triage team

   c: new featureNothing broken; request for a new capabilityNothing broken; request for a new capability

   c: proposalA detailed proposal for a change to FlutterA detailed proposal for a change to Flutter

   refactorImproving readability/efficiency without behavioral changesImproving readability/efficiency without behavioral changes

   frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.

   p: material_uimaterial_ui package in flutter/packagesmaterial_ui package in flutter/packages

   team-designOwned by Design Languages teamOwned by Design Languages team

   and removed

   in triagePresently being triaged by the triage teamPresently being triaged by the triage team

   on Sep 19, 2025
2. dkwingsmt

   added

   P3Issues that are less important to the Flutter projectIssues that are less important to the Flutter project

   triaged-designTriaged by Design Languages teamTriaged by Design Languages team

   on Sep 24, 2025
3. dkwingsmt commented on Sep 24, 2025

   

   dkwingsmt

   on Sep 24, 2025

   Contributor

   More actions

   Tab bars are indeed common design patterns. Cupertino also has its own tab bar widget. I think in general having some form of a tab bar widget in the widgets library is reasonable, although the exact form still needs more discussion. For example, an alternative way would be to introduce a RawTabBar. Anyway, this should not be executed at least until material and cupertino have been moved to their individual packages.

   Also related: #97496
4. Piinks

   added this to Decoupling Designon Nov 5, 2025
5. justinmc commented on Aug 7, 2026

   

   justinmc

   on Aug 7, 2026

   Contributor

   More actions

   I agree with this. We should investigate a RawTabBar abstraction between TabBar and CupertinoTabBar as @dkwingsmt said, and move over other related classes that are not specific to Material.

   👍React with 👍1Reacted by Francesco Iapicca
6. Piinks

   added

   packageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.

   and removed

   frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.

   on Aug 17, 2026
7. navaronbracke commented on Oct 1, 2026

   

   navaronbracke

   on Oct 1, 2026

   Contributor

   More actions

   I think I'll look into this, since it partially blocks decoupling test/widgets/navigator_test.dart, for the decoupling project.

   Maybe I can move some things over already.
8. navaronbracke

   assigned

   navaronbracke

   and unassigned

   navaronbracke

   on Oct 1, 2026
9. navaronbracke commented on Oct 2, 2026

   

   navaronbracke

   on Oct 2, 2026

   Contributor

   More actions

   TabController & TabBarView seem easy to move out of Material. (no real dependency on Material) Cupertino does not yet use a TabController, so there's a bit of friction there.

   The Tab class can also be moved out of Material fairly easily. (we can probably provide parameters for the things like tab height)

   TabBar on the other hand is quite complex, because it has a bunch of Material specific things baked in.