Kael

There is also `floating` which applies a 12px offset or 8px with `dot`. I think the intention with `inline` was to use it standalone *next to* something instead of having...

I don't think we should have a separate way of positioning it just for this, inline should only be used without anything inside: https://play.vuetifyjs.com/#eNpVjs0KwjAQhF8lLB6txavEgs9hPMRmWwJxDWlS/MF3dxMjtJdld+ZbZs5vmELfnrzfzQnhADLizTsdsVMkhJwb7X1Zy9HfKWpLGKpUxKs2IwpLjg2RCaR4VLBX0Mm22kveMiPyYGjDqdEOTwVisi9k5dE4HUaszxn7x/O5zs/Kr55sF7UTGRwYMorgs6XkXBmXL0iGTfw=

Yeah this is all in vue and vue-router's code, I imagine you'd get the same thing if you had 1000 components with just `useLink(props)`

I don't know what you expect me to do about this, getCurrentInstance is exported https://unpkg.com/[email protected]/lib/util/index.mjs

Confirmed broken in beta 0, probably #20038

Supporting null precision doesn't seem particularly complicated ```diff --- a/packages/vuetify/src/labs/VNumberInput/VNumberInput.tsx +++ b/packages/vuetify/src/labs/VNumberInput/VNumberInput.tsx @@ -55,7 +55,7 @@ const makeVNumberInputProps = propsFactory({ default: 1, }, precision: { - type: Number, + type:...

> After decrement I get 3.0519999999999996 Yeah that's pretty lame. I'm fine with having 0 by default.

How about `v-slots="$slots"` like jsx? Full passthrough would just be `` ```html ... ``` equivalent to jsx ```jsx {{ ...slots, foo: () => ... }} ```

Also #1155 These strict runtime checks are incredibly inconvenient, I don't understand why you need to throw an error (often breaking the entire page) when just passing through null values...

I already tried that. I also can't see it in `docker images` or `docker ps -a`.