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 May 29, 2019. It is now read-only.
The current tab design is problematic as I need to toggle between two tabs if a variable is true or false. But if I put active="condition" on one and active="!condition" on the other it causes activation bugs (both are potentially active).
I don't get why keys or headings are not used instead and <tabset ng-model="active"> is used instead.
The text was updated successfully, but these errors were encountered:
The current tab design is problematic as I need to toggle between two tabs if a variable is true or false. But if I put
active="condition"
on one andactive="!condition"
on the other it causes activation bugs (both are potentially active).I don't get why keys or headings are not used instead and
<tabset ng-model="active">
is used instead.The text was updated successfully, but these errors were encountered: