Hihi… learned something new with this. Vue adds the component instance to an array element in a v-for with refs. So, you have to access the first element of the array to get the underlying component internals. Yet, if you set a ref outside a v-for loop, the instance is directly on the named element of the $refs array. Hmm…

Getting back to your challenge… name isn’t a QBtn property. If you add it additionally, it’s an attribute. Check my codepen now, if that is what you are looking for.

https://codepen.io/smolinari/pen/YzpoBdR?editors=1010

If not, I’d tend to believe you are trying to accomplish something that is not standard practice with Vue. If you’d explain your use case better, we might be able to help you find the right path to a better solution.

Scott

@jj

If you want better support please create a working codepen.io that demo’s your problem.

@donsherman it’s in the comments, as to what promises are, read it in the mdn or somewhere. Don’t really need promises in the example, just implement your own logic to traverse all tabs on mounted as to solve the refs being undefined.

It works!
Thank you