Description
Feature Description
When enableing tab navigation, I have to use mat-tab-nav-bar
instead of mat-tab-group
. Works great, but removes the transition animation between the tabs (sliding left / right).
There are some other related issues about it: #15570, #18169
I cannot accept the answer that I should use mat-tab-group
instead. The reason using mat-tab-nav-bar
is the tab navigation over URL, etc. Or do you generally not recommend this? If yes why?
The workaround in the other solution works. But I wonder, why not just implement this this framework? Since the mat-tab-group
already has this animation. What is the reason for refusing such a legitimate request?
I don't like to write code / workaround for stuff that should actually be part of the framework. Custom data with index for the animation, etc.
No offense, I was just wondering what the problem is. Together we could think about an elegant solution. Maybe a directive for the router-outlet
container? But how to detect left and right sliding? (See workaround #18169)
Use Case
Just be consistent to mat-tab-group
. Why not? Why should we regret implementing tab navigation using mat-tab-nav-bar
. Which is an awesome feature? Just complete the implementation by adding the same animation like in mat-tab-group
.