Jukka Raimovaara

@VividLemon for this to work we'd need to wrap BLink in a span. Directives aren't supported on multiroot components / fragments. Should we have a tooltip booleanis on the BLink...

fixed in 0.8 without nuxt: https://stackblitz.com/edit/vue-o27vjt?file=src%2FApp.vue I'm not sure what the first nuxt example is trying to do. But dynamic title is working in 0.8 @VividLemon close

@floating-ui/vue is a low level vue bindings for Floating ui core library. It's meant for building your own floating elements. floating-vue is a complete solution with components and styles.

You didn't link to a tab implementation only to an nav implementation... little confused about what you're after... You mean like this: https://bootstrap-vue-next.github.io/bootstrap-vue-next/docs/components/nav.html#dropdown which is what you linked, but either...

imho. We already have type="datetime-local" so we don't need a picker anymore in the main libary. I have bootstrap style date/time -pickers in one client project, I could maybe clean...

@dword-design-honestly yes, that's why they work universally, and on mobile I prefer the native widget over any other picker.

@VividLemon imho, I'm two minds about this. I'd like to keep the core components simple. Maybe have another repo for more complex components that aren't "bootstrap"... but we already have...

@VividLemon if the :to in teleport is undefined, the disabled teleport won't render in ssr 😆 there is even a pull request about it for months: https://github.com/vuejs/core/pull/9783/files `:to="teleportTo || 'body'"...

Super weird. Might be some optimization that vue does when single children component.

It happens because tab is a computed that runs the buttonId which is useId the first time in the provide context, in this fix it's run in the setup context....