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 has been archived by the owner on Dec 8, 2022. It is now read-only.
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
Create a sky-tabset with two tabs.
Set the tabIndex to 0 for the first and 1 for the second.
Add an ngIf to the second tab
Add a handler for the tabset's activeChange event and view the index that is passed into this handler.
Notice that when you click on the first tab 2 is returned instead of 0
Expected behavior
I would expect the
tabIndex
property to function even when one tab has anngIf
Actual behavior
When setting
tabIndex
to a number and one of the tabs has anngIf
the tabset does not recognize thetabIndex
correctly. This does not happen if you use a string for thetabIndex
property instead of a number.Steps to reproduce
sky-tabset
with two tabs.tabIndex
to 0 for the first and 1 for the second.ngIf
to the second tabactiveChange
event and view the index that is passed into this handler.2
is returned instead of0
Plunker
https://plnkr.co/edit/5deoHax1yz4kryhk5r6L?p=preview
The text was updated successfully, but these errors were encountered: