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 was archived by the owner on Apr 12, 2024. It is now read-only.
I noticed some odd ngClass behavior when upgrading from Angular 1.0.1 to 1.0.3. Going back to 1.0.2 fixed the problem. The following fiddle illustrates the problem:
Since a is false initially, the text should get the "foo" class and be red. The watch kicks in immediately and changes a to true, which should remove the "foo" class from the text and thus change it back to black. This is what happens in Angular 1.0.2, but not in 1.0.3.
(In my real app, I have two Twitter Bootstrap tabs that become initially active at the same time due to this bug.)