[Tabs] Prevent user from activating/deactivating tabs

[Daeluse]

Bug, feature request, or proposal:

Feature Request

What is the expected behavior?

Following a similar function to how canActivate and canDeactivate works on Routing, it would be extremely beneficial to have a way to run a check before allowing a tab to be activated or deactivated.

What is the use-case or motivation for changing an existing behavior?

Within the tabs, if a user is able to change a setting or edit information and the user is required to click 'save' before the changes are committed, there should be a way to prompt the user of the existing changes before they can navigate away, by switching tabs or routes. The necessity here would be that we would need a way to check both on tab switch and route switch without (hopefully) having to duplicate code.

[PhilHuot]

Would be really nice to have.

[angular-robot]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[angular-robot]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.