-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] - fwChange event for fwTabs #106
Labels
Comments
asif-ahmed-1990
pushed a commit
that referenced
this issue
Aug 14, 2020
fwChange was firing twice. This fixes and makes it fire once. fix #106
6 tasks
asif-ahmed-1990
pushed a commit
that referenced
this issue
Aug 14, 2020
fwChange was firing twice. This fixes and makes it fire once. fix #106
github-actions bot
pushed a commit
that referenced
this issue
Aug 14, 2020
## [2.3.3](v2.3.2...v2.3.3) (2020-08-14) ### Bug Fixes * **fw-tabs:** fwChange fires twice ([0135302](0135302)), closes [#106](#106)
🎉 This issue has been resolved in version 2.3.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 2.3.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component
fwTabs
Describe the bug
The fwChange event for fwTabs is being fired twice and before the tab is fully shown. So I can't get the current activeTabIndex property.
To Reproduce
Steps to reproduce the current behavior:
Changing tabs will result in two outputs in the console with the previous tab index.
Expected behavior
Event should be fired once and after the tab is fully shown, so getting the activeTabIndex would returns the current index.
The text was updated successfully, but these errors were encountered: