Description
Bug, feature request, or proposal:
Feature request
What is the expected behavior?
"md-tab-nav-bar" component to have same functionality / visual fidelity as the "md-tab-group" component.
What is the current behavior?
The 2 components are disjoint and improvements made in "md-tab-group" component won't show up in the "md-tab-nav-bar" component
What are the steps to reproduce?
See the default demo included in this repository
What is the use-case or motivation for changing an existing behavior?
I am building a large application that uses lazy loaded modules to implement specific features. I want to display specific functionality in tabs. For example we have a customer object which can contain up to 11 tabs which represent specific data pertaining to this customer.
The current "md-tab-group" implementation is already looking great (Dynamic height, scrolling, pagination when tabs exceed container width etc..) But with the "md-tab-nav-bar" component none of these features are available.
Which versions of Angular, Material, OS, browsers are affected?
Material 2.0.0-alpha.11