Jukka Raimovaara
Jukka Raimovaara
Really can't say this rings any bells. And I've never used rsbuild, just vite all the time. b-modal should not modify the dom outside of it self (or the teleport...
I strongly recommend moving to nuxt for ssr. I've even forked vite-ssr (https://github.com/flow-tools/vite-ssr) to keep it up-to-date for a project. But I'm gonna convert that to nuxt when I have...
> Regarding point 2, I investigated more and it's unlikely that BVN is to blame. > > It seems that any disabled teleport in my app causes problems: > >...
Use a component, the directives are a hack anyway. I'll look if we can even make this work with directives.
you need to add an id for the tab for the index to find the correct one. It's quirk at the moment, haven't figured a good way to fix it....
@susanne99 you know that id:s are also props? Almost every vue ui library uses them all over the place to identify components in the component render tree, it has nothing...
How would data attributes change the thing? We are not waiting for the dom because that breaks SSR rendering. The old implementation was waiting, but then there was no tab...
"ok" doesn't change anything if prevented... So it closes or doesn't close? or the change emit doesn't close it? What promise should be waited and by what?
PostGraphile also uses LISTEN/NOTIFY for realtime subscriptions. https://www.graphile.org/postgraphile/subscriptions/
The whole reactivity with the directive is a little hacky. I'll reimplement the whole directive when I have to time and the PR #2732 is finalized. I'll take a look...