question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Iterative tabs +constant tab issue

See original GitHub issue

If we have the following tabs:

<b-tabs card>
    <b-tab :title="`${tabz[key].nativeName}`" v-for="(lang, key, i) in tabz" :key="i">
        Tab Contents: {{tabz[key].name}}
    </b-tab>
    <b-tab title="+">
        Plus tab content
    </b-tab>
</b-tabs>

… everything is fine if the tab’s data is already loaded on the page like this:

        data () {
            return {
                tabz: {
                    bg: {
                        name: "Bulgarian",
                        nativeName: "Български"
                    },
                    en: {
                        name: "English",
                        nativeName: "English"
                    }
                },
                ....

… but if the data comes later(from server) the result is that two tabs will be selected (the first one(Bulgarian) and the ‘+’ tab) and we will see the content of the both selected tabs together. This can be simulated like this:

        data () {
            return {
                tabz: null,
                ...


        created () {
            setTimeout(() => {
                this.tabz = {
                    bg: {
                        name: "Bulgarian",
                        nativeName: "Български"
                    },
                    en: {
                        name: "English",
                        nativeName: "English"
                    }
                }
            }, 1000);

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:10 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
tmorehousecommented, May 29, 2017

What might happen is that the same tab index or active tab will be selected on update of the tabs content (to keep current functionality when adding tabs to the end). Of which you could then issue a set active tab to reset it to index 0 (via v-modal) after your update.

1reaction
tmorehousecommented, May 29, 2017

OK, I think I can fix this relatively easily for next release.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Clicking on tabs randomly shifts the tab out of the window and ...
Issue 1270828: Clicking on tabs randomly shifts the tab out of the window ... In specific cases the driver doesn't handle constant register...
Read more >
Tab Error in Python - Stack Overflow
When invoking the Python 2 command line interpreter with the -t option, it issues warnings about code that illegally mixes tabs and spaces....
Read more >
how to allow tabs to be viewed during runtime - NI Community
I want to be able to select a tab during runtime and view it. ... on every iteration because I kept receiving a...
Read more >
Tabs.do: Task-Centric Browser Tab Management
4.5 [D3] Prioritizing. One issue with the current browser tab design is that it does not reflect users varying task types and priorities....
Read more >
tab-size - CSS: Cascading Style Sheets - MDN Web Docs
The tab-size CSS property is used to customize the width of tab ... width of the space character (U+0020) to be used as...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found