Skip to content
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.

Tabs - tabIndex property malfunctions when using a "number' index and a tab with "ngIf" #1631

Closed
Blackbaud-TrevorBurch opened this issue Apr 16, 2018 · 2 comments

Comments

@Blackbaud-TrevorBurch
Copy link
Member

Expected behavior

I would expect the tabIndex property to function even when one tab has an ngIf

Actual behavior

When setting tabIndex to a number and one of the tabs has an ngIf the tabset does not recognize the tabIndex correctly. This does not happen if you use a string for the tabIndex property instead of a number.

Steps to reproduce

  1. Create a sky-tabset with two tabs.
  2. Set the tabIndex to 0 for the first and 1 for the second.
  3. Add an ngIf to the second tab
  4. Add a handler for the tabset's activeChange event and view the index that is passed into this handler.
  5. Notice that when you click on the first tab 2 is returned instead of 0

Plunker

https://plnkr.co/edit/5deoHax1yz4kryhk5r6L?p=preview

@Blackbaud-TrevorBurch
Copy link
Member Author

Oddly enough this only happens when using indexes 0 and 1. It appears to work if I change the two tabs to use tabIndex properties of 3 & 4.

@Blackbaud-AlexKingman
Copy link
Contributor

Closed via #1878

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

No branches or pull requests

2 participants