Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: initialize $scope.$tabSelected when nested tabs selected.
Like the issue #1276 if you have some nested tabs, you select a sub-tab item, and you will active some other siblings, because when tabCtrl add every new $scope, it does't has a initial attr $scope.$tabSelected, so every unselected item will read the $tabSelected from inherited $parent, but if the parent-tab has been actived, the all of its sub-tabs will read this true property in $scope.$tabSelected. So I think we should initialize the property $scope.$tabSelected before invoking tabsCtrl.add(), and every tab-item will has a 'false' status for a initial $scope.$tabSelected.
- Loading branch information