active two-way data binding is broken in 1.2.0 and 1.2.1

[WillBDaniels]

Bug description:

The 2-way data binding for the 'active' attribute in the tab component seems to be completely broken with the latest two versions. I'd give a plnkr, but plnkr is giving me a helluva time loading the latest js, in fact, so is jsfiddle. here's a working example: https://jsfiddle.net/willbdaniels/2mq3106a/14/ it just has the js I needed (1.2.0) embedded. you can change the raw js around to see the problem not being present in the version just before that

Version of Angular, UIBS, and Bootstrap

Angular: 1.4.8

Bootstrap: 1.2.1

Edit to add in nice plunker

http://plnkr.co/edit/GkyGI4V92I4DXp3CWYwp

[icfantv]

@WillBDaniels, you can use the 'Edit in Plunker' link from our demo page to create a basic working plunker you can use to reproduce your issue. Your instructions are a little vague so we're going to need a plunker that shows the issue. Thanks.

[WillBDaniels]

@icfantv alright, I think i got the plunk working, you can see the behaviour here: http://plnkr.co/edit/GkyGI4V92I4DXp3CWYwp

Namely, you'll notice that the $scope.activeTab is being completely unaffected by the 'active' property on the uib-tab. Then, if you change the ui-bootstrap version to '1.1.2' in the index.html instead of 1.2.1, the behaviour goes back to normal, and all $scope variables are respected again.

[icfantv]

Thank you. I was able to confirm this as an issue in our application at work as well. Marking as a bug.

[wesleycho]

This is not a bug - the active attribute was changed, as noted in the changelog. The new usage is shown in the example.

Here is a working Plunker

[icfantv]

@WillBDaniels, with apologies for the team, this should have been marked as a breaking change so it showed up in the change log. It wasn't so it didn't. I will update when I get to work.