First of all, I never mentioned how I LOVE this angular-material project.
Here's the codepen example:
http://codepen.io/yccteam/pen/GgGbzO
The issue is this:
- Tabs are created and work fine.
- When I click on "Change IF" the tabs are supposed to disappear due to
ng-if - works great.
The problem is:
- When "Change IF" is clicked again, the `ng-if
is satisfied and shows the tabs again. butmd-select`` isn't taken into account once the tabs reappear.
I've also added the "ng-show" for sports (just click "Change SHOW" to play with it).
It works, but now I need to take care of the md-bar, which is external to the tab itself.
I currently sove this using a hack with a watcher that sorts things out, but using a watcher while I already have a watcher (ng-if) seems very... hackish...
Is this behavior intentional? Any way to solve this within the API?
Added later:
I've added another functionality that recreates a bug in the tabs:
- Click on the "Change SHOW" in order to make the tabs to disappear.
- Then click on the "Change Tab" until the tab index changes (the number below the button)
- Click on "Change SHOW" in order to make the tabs reappear.
- Note the tabs appear wrong
First of all, I never mentioned how I LOVE this angular-material project.
Here's the codepen example:
http://codepen.io/yccteam/pen/GgGbzO
The issue is this:
ng-if- works great.The problem is:
is satisfied and shows the tabs again. butmd-select`` isn't taken into account once the tabs reappear.I've also added the "ng-show" for sports (just click "Change SHOW" to play with it).
It works, but now I need to take care of the
md-bar, which is external to the tab itself.I currently sove this using a hack with a watcher that sorts things out, but using a watcher while I already have a watcher (
ng-if) seems very... hackish...Is this behavior intentional? Any way to solve this within the API?
Added later:
I've added another functionality that recreates a bug in the tabs: