Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hydration style mismatch on <VMain /> #232

Closed
Endermanch opened this issue Jun 6, 2024 · 1 comment · Fixed by #199
Closed

Hydration style mismatch on <VMain /> #232

Endermanch opened this issue Jun 6, 2024 · 1 comment · Fixed by #199
Labels
bug Something isn't working

Comments

@Endermanch
Copy link

This should be fixed ASAP

The most basic functionality of providing the layout for the application is broken.

image

Reproduction:

<VApp full-height theme="light">
  <VLocaleProvider locale="ru">
    <VLayout>
      <NuxtLoadingIndicator />
      <NuxtLayout>
        <Header /> <!-- vappbar + vnavigationdrawer -->
        <VMain>
          <NuxtPage />
        </VMain>
        <LazyFooter app /> <!-- vfooter -->
      </NuxtLayout>
    </VLayout>
  </VLocaleProvider>
</VApp>

Temporary resolution:
Just hardcode the styles. This will break if any of the layout elements have dynamic width/height.

<VMain
  style="
    --v-layout-left: 0px;
    --v-layout-right: 0px;
    --v-layout-top: 110px;
    --v-layout-bottom: 300px;
  "
>
@userquin
Copy link
Member

userquin commented Jul 20, 2024

Try moving the content to layouts/default.vue: check https://github.com/userquin/nuxt-vuetify-issue-205-v-issue-19015/tree/nuxt-vuetify-issue-232 (there is a PR with the changes).

It seems Vuetify with same problem related to #205 (comment) (when enabling ssr client hints we get missmatch warning about drawer z-index, when disabling ssr client hints the missmatch warning about app footer left position)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants