-
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
Fix #12245 does not seem to be part of the released package 6.4.1 #12386
Comments
Can reproduce that as well. (https://unpkg.com/@angular/material@6.4.1/bundles/material-tabs.umd.js). @josephperrott can you have a look? |
Can also reproduce on the current documentation site: demo, "Tab group with dynamically changing tabs". select the "select tab after editing" checkbox and then "Add new tab". The selected tab does not change. Note, it does work occasionally as you edit the selected index textbox, but when the add button creates a tab and changes the selected tab index textbox, the tab does not change. |
It looks like something went wonky with our release process and the fix should be included in our next patch release. |
Closing as this change is included in |
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. |
Bug:
The fix #12245 does not seem to be part of the generated npm package located at https://registry.npmjs.org/@angular/material/-/material-6.4.1.tgz (see function MatTabGroup.prototype.ngAfterContentInit function for example).
The release source archive does contain the fix.
What is the expected behavior?
What is the current behavior?
What are the steps to reproduce?
Providing a StackBlitz reproduction is the best way to share your issue.
StackBlitz starter: https://goo.gl/wwnhMV
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 6.1
Angular Material 6.4.1
Windows 10
Typescript 2.7.2
Chrome 67
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: