Skip to content
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

bug(mdc-tabs): animationDuration does not affect the tab indicator #24036

Open
andrewseguin opened this issue Nov 30, 2021 · 3 comments
Open
Labels
area: material/tabs feature This issue represents a new feature or feature request rather than a bug or bug fix needs: discussion Further discussion with the team is needed before proceeding P4 A relatively minor issue that is not relevant to core functions

Comments

@andrewseguin
Copy link
Contributor

andrewseguin commented Nov 30, 2021

The tab config's animationDuration should affect the tab indicator.

@andrewseguin andrewseguin added the needs triage This issue needs to be triaged by the team label Nov 30, 2021
@andrewseguin
Copy link
Contributor Author

The general solution we expect external users to use is to just override the styles themselves by targeting the element and applying a different transition duration. However, internal users are discouraged from making these style changes.

Team has to agree whether it is worth it to sync the duration values - e.g. if the content moves twice as fast or slow, does it look right for the indicator to also go twice as fast or slow. Since this is out of spec, there is no easy correct answer

@crisbeto crisbeto added area: material/tabs feature This issue represents a new feature or feature request rather than a bug or bug fix needs: discussion Further discussion with the team is needed before proceeding P4 A relatively minor issue that is not relevant to core functions and removed needs triage This issue needs to be triaged by the team labels Dec 6, 2021
@angular-robot
Copy link
Contributor

angular-robot bot commented Mar 14, 2022

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
Copy link
Contributor

angular-robot bot commented Apr 3, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: material/tabs feature This issue represents a new feature or feature request rather than a bug or bug fix needs: discussion Further discussion with the team is needed before proceeding P4 A relatively minor issue that is not relevant to core functions
Projects
None yet
Development

No branches or pull requests

2 participants