You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.
I can confirm this. Upgraded from 0.83 to 0.9 RC3 today and found this not working at all.
I debugged a little in the sources and found that the expressions given in md-on-select/deselect are executed in the wrong scope. It is executed agains the md-tabs parent scope which does not know anything about the scope created by ng-repeat on md-tab level.
So instead of evaluating the md-select expression against the md-tabs scope it has to be executed against the individual tab's scope (or parent scope, which would be the scope created by ng-repeat).
In addition to the behavior above, I'm also missing the very first tab select event after the ng-repeat has been executed. The method calling the select/deselect functions is only called when the tab list is still empty and not when it is has been populated by ng-repeat.
The following plunkr demonstrates the problem:
http://plnkr.co/edit/c4Qmb5RBdH4jAHbR9ET6?p=preview
As you can see from the demo, the tab is generated correctly. But, the expression evaluated in md-on-selected doesn't recognize the tab parameter.
The text was updated successfully, but these errors were encountered: