-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
<b-tabs> loss of <b-tab> control as of rc20 when used in modals #3361
Comments
Just experienced the same after closing and reopening the modal. Here is some easy replication code.
|
Hmm... strange that this issue is back. will have to investigate. Confirmed in the latest |
Yes, I can confirm the same behavior in the latest version.
Am 23.05.2019 um 14:38 schrieb T Morehouse <[email protected]<mailto:[email protected]>>:
Hmm... strange that this issue is back. will have to investigate. Confirmed in the latest dev branch as well
https://deploy-preview-3289--bootstrap-vue.netlify.com/
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#3361?email_source=notifications&email_token=AJ5GLWNYPAE3JOSVZ4XLJRLPW2F2RA5CNFSM4HO3VJQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWCCULA#issuecomment-495200812>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AJ5GLWPSCAE66C2WIQOTX43PW2F2RANCNFSM4HO3VJQQ>.
|
For a workaround, set the |
Works with static, but now the modal pops up again right after you close it^^
Am 23.05.2019 um 15:45 schrieb T Morehouse <[email protected]<mailto:[email protected]>>:
static
|
@F-Node-Karlsruhe I didn't see that issue (modal popping up again on close) when I confirmed the issue and tried the |
Static prop is working. |
Describe the bug
If you put b-tabs inside of a modal, upon opening the modal for the first time everything works fine, but if you close the modal and reopen it, then the tabs don't work, it will be stuck on the content of the first tab, and switching tabs will not have any effect, instead the content of the first tab will remain visible. Reloading the page is the only way to get it to work again.
Steps to reproduce the bug
https://jsfiddle.net/gh9y7zLs/2/
Versions
Libraries:
Environment:
The text was updated successfully, but these errors were encountered: