Tab initial selection

[bsr203]

Please find the plnkr

http://plnkr.co/edit/RCVFji2Upl4VRAoiAcZE?p=preview

I do my setting as (all static tabs)

 $scope.tabsettings = {
    a: {},
    b: {active: true}
  };

But, something overrides it, and the first tab become selected by default.

[pkozlowski-opensource]

@ajoslin I think I've fixed most of the bugs for 0.5.0 and just want to review datepicker changes before cutting the release. Would be awesome if you could have a look at this one - I had a quick look and it is still reproducible with the latest master.

[raykin]

@bsr203 I also got the same problem in my project. And I fix it locally. Please check the diff of https://github.com/raykin/bootstrap/commit/97f6f64163a7e93120adba198f80fd882f29ac6d and update your local code.
The reason of this bug is twice loop of nested watch which always set the active of first tab as true and others as false

         scope.$parent.$watch(getActive, function updateActive(value) {
            scope.active = !!value;
          });
        scope.$watch('active', function(active) {
          setActive(scope.$parent, active);
          if (active) {
             // ....

the above watch are triggered by

       tabsetCtrl.addTab(scope, true);
        // it finally trigger
       angular.forEach(tabs, function(tab) {
         tab.active = false;
       });

my fix is add a check to stop the trigger when compile the tab directive.
but it's not a perfect fix, it requires explicitly set active tab, or you will got a non selected tabset when page init rendered.
Also I run the test suits, only one test which mentioned above failed. So @bsr203 you can use the fix at now without worry about other breaks.