Vue hydration silently drops class attribute updates when SSR and client render different branches of a v-if chain — per the project's Auth SSR Pattern, useAuth is client-only and server always renders unauthenticated, so PageHeader (v-else branch) was rendering inside a leftover .loading / .loading-state div from the v-else-if branch. On mobile that div was being masked by the visual-test commonMasks (.loading-state), producing a large fuchsia block in the snapshot. Wrapping the v-if/v-else-if/v-else chain in <ClientOnly> ensures the server renders nothing for the auth-gated content and the client performs a clean first render, matching the pattern already used in dashboard.vue. Also update admin-dashboard-desktop for minor anti-aliasing drift. |
||
|---|---|---|
| .. | ||
| about | ||
| admin | ||
| auth | ||
| events | ||
| member | ||
| members | ||
| series | ||
| about.vue | ||
| accept-invite.vue | ||
| coming-soon.vue | ||
| connections.vue | ||
| index.vue | ||
| join.vue | ||
| login.vue | ||
| peer-support.vue | ||
| verify.vue | ||
| welcome.vue | ||