Jukka Raimovaara

more missmatch stuff from upstream: nuxt: https://github.com/nuxt/nuxt/issues/27378 vue core: https://github.com/vuejs/core/issues/6638 so if using ssr, set your own id:s for the components

@VividLemon Also noticed that: [nuxt] `useId` might not work correctly with components that have `inheritAttrs: false` so we maybe need to pick the https://github.com/nuxt/nuxt/blob/4d063f1f85cf53f4fa97978f3f8724aacb24174a/packages/nuxt/src/app/composables/id.ts#L5 (data-n-ids) nuxt attrs and put that...

There seems to be a lot of fixes in vue 3.5 for ssr! Let's see if it's new useId also fixes our problems. We should maybe use that directly instead...

Have you tested that it works like passive: true? I'm not 100% sure about that.

To answer my own question, vue should detect if there isn't an variable in the prob it creates a local one

does spread add something in babel? eg. ``` {...localeConfig[c], ...customConfig[c]} ``` or do we need a helper function like: ```javascript function m(o1,o2){ var o = {}; for (var attrname in...

@VividLemon any thoughts on this one?

@VividLemon do you also agree that we should remove this from popover/tooltip? some people might be using v-tooltip="very important tooltip". I think we should guide these people to use a...

IMHO, if it's just one search and replace on the codebase, I don't think we need to worry about this. Just document the change to a migration guide. or something...

> @xvaara Because tooltips are rendered next to the element, how should we handle this? It hardly seems appropriate to make some hacky css to make it so tooltips are...