-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mat-tab-group with mat-stretch-tabs stretches tab groups inside it #12196
Labels
P4
A relatively minor issue that is not relevant to core functions
Comments
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jul 13, 2018
Fixes `mat-stretch-tabs` applying to all descendant tab headers, rather than direct descendants only. Fixes angular#12196.
jelbourn
pushed a commit
that referenced
this issue
Aug 23, 2018
Fixes `mat-stretch-tabs` applying to all descendant tab headers, rather than direct descendants only. Fixes #12196.
jelbourn
pushed a commit
that referenced
this issue
Aug 23, 2018
Fixes `mat-stretch-tabs` applying to all descendant tab headers, rather than direct descendants only. Fixes #12196.
jelbourn
pushed a commit
that referenced
this issue
Aug 29, 2018
Fixes `mat-stretch-tabs` applying to all descendant tab headers, rather than direct descendants only. Fixes #12196.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug, feature request, or proposal:
When adding a mat-tab-group inside a mat-tab-group with mat-stretch-tabs it behaves as if if it has mat-stretch-tabs.
What is the expected behavior?
A mat-tab-group inside a stretching mat-tab-group with mat-stretch-tabs shouldn't stretch.
What is the current behavior?
A mat-tab-group inside a stretching mat-tab-group with mat-stretch-tabs stretches.
What are the steps to reproduce?
https://stackblitz.com/edit/angular-material2-issue
What is the use-case or motivation for changing an existing behavior?
TABCEPTION
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
6.3.3
Is there anything else we should know?
No, you're smart.
The text was updated successfully, but these errors were encountered: