Kal
Hydration hell - A simple loading state on a Nuxt UI button
If this is the case, you probably want to look at somehow excluding the actual
<button> from being cached; maybe there's an attribute to tell Firefox "hey, this isn't part of a form, so don't cache it's state".79 replies
Hydration hell - A simple loading state on a Nuxt UI button
The FF hydration errors go away when simply removing the disabled attribute on the
<button>.
I wonder if it's related to this:
Firefox behaves different than all browsers when it comes to caching of form element states (e.g. button disabled state).
https://bugzilla.mozilla.org/show_bug.cgi?id=65407279 replies
layout slot issue
I didn't scrub through all of AI's hogwash regurgitation...
In any case, on a quick glance, this to me looks like multiple child elements:
This is multiple root elements, and seems strange to do:
<template>
<NuxtLayout>
<NuxtPage />
</NuxtLayout>
<UModals />
<UNotifications />
</template>
Instead, I would expect (a single root element):
<template>
<NuxtLayout>
<NuxtPage />
</NuxtLayout>
</template>
and in your Layout (wherever/whatever it is) you'd keep <UModals /> and <UNotifications />.
Relevant doc:
https://nuxt.com/docs/guide/directory-structure/layouts#enable-layouts
Unlike other components, your layouts must have a single root element to allow Nuxt to apply transitions between layout changes - and this root element cannot be a <slot />.
22 replies