[Tabs] Tab label not fully shown when added past overflow
- Langage dominant
- TypeScript
- Étoiles
- 25k
- Forks
- 6.8k
- Merge moyen
- 1 j 8 h
- PR mergées (30 j)
- 91
Description
#### Bug, feature request, or proposal:
Bug
#### What is the expected behavior?
Tab is selected after being added to mat-tab-group and is in full view.
#### What is the current behavior?
Tab is selected and is hidden behind the paginators.
#### What are the steps to reproduce?
https://stackblitz.com/edit/angular-material2-issue-c9hsyv
In the stackblitz above, add tabs until the paginator is shown. The tab will be partial hidden by the paginator.

#### What is the use-case or motivation for changing an existing behavior?
Navigating the user to the tab they just opened.
#### Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular: any
Material: 5.0.0
OS: any
TypeScript: 2.4.2
Browsers: any
#### Is there anything else we should know?
A related issue which can also be seen in the stackbliz provided, is that the transform of the bar is not correctly updating when removing tabs. Steps to reproduce: Add 4(or enough tabs to show pagination) tabs (pagination will be shown and last tab will be selected).
Remove the third tab by clicking the X on the label. Pagination is shown until clicking on the label. It then updates and removes the pagination controls since the content can fit.


Both issues seem to be related to the animation of the inkbar. (ink-bar.ts line 35) Performing the left calculation in the animation frame plus the delay of the actual animation happens after all the calculations to show/hide the paginator controls.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Reproduisez les cas de débordement et de suppression d’onglets dans le StackBlitz lié, puis examinez ink-bar.ts autour de la ligne 35 ainsi que le comportement de pagination des onglets. Confirmez qu’un onglet sélectionné nouvellement ajouté est entièrement visible et que la suppression d’un onglet met à jour le paginateur sans clic supplémentaire ; couvrez ces deux comportements avec des tests de régression si le point d’entrée de test pertinent est trouvé.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- angular, typescript
- Domaine
- frontend
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100