Skip to content
This repository has been archived by the owner on May 29, 2019. It is now read-only.

Issue with UI.Bootstrap.tabs control #2744

Closed
rajeevp opened this issue Sep 24, 2014 · 3 comments
Closed

Issue with UI.Bootstrap.tabs control #2744

rajeevp opened this issue Sep 24, 2014 · 3 comments

Comments

@rajeevp
Copy link

rajeevp commented Sep 24, 2014

Serious issue with tab control, when we have "select" action assigned and navigate to the next page (it means "$destroy" will be fired). It calls the select method for following tabs..
E.g. Tab1 | Tab2 (selected) | Tab3 | Tab4.

When we navigate to next page it fires "select" event for Tab3 and Tab4. Basically event is being triggered when $destroy->removeTab method

@irnes
Copy link

irnes commented Sep 25, 2014

I have noticed the same issue. I use the tab select action to trigger a REST API call. So as soon as I leave an active view the select event is triggered for all tabs what causes unwanted REST API calls.

@Coridyn
Copy link
Contributor

Coridyn commented Sep 30, 2014

I've just encountered this issue as well. It looks like pull request #2596 addresses this issue but needs a test case before it can be merged.

@chrisirhc
Copy link
Contributor

Closing this as it was supposed to be fixed with #2763 .

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants