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

[ssr] Hydration error with animateTransform node #3243

Closed
rstoenescu opened this issue Feb 16, 2021 · 0 comments · Fixed by #3247
Closed

[ssr] Hydration error with animateTransform node #3243

rstoenescu opened this issue Feb 16, 2021 · 0 comments · Fixed by #3247
Labels
🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. 🐞 bug Something isn't working scope: ssr

Comments

@rstoenescu
Copy link

Version

3.0.5

Reproduction link

https://github.com/rstoenescu/vue3-ssr-bug-animate-transform

Steps to reproduce

  1. yarn
  2. yarn dev
  3. Check browser console

What is expected?

Should not have any hydration errors

What is actually happening?

Has hydration error

[Vue warn]: Hydration node mismatch:
- Client vnode: animateTransform
- Server rendered DOM: <animatetransform>​</animatetransform>​
  at <Home onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< undefined > >
  at <RouterView>
  at <App>
@rstoenescu rstoenescu changed the title Hydration error with animateTransform node [ssr] Hydration error with animateTransform node Feb 16, 2021
@HcySunYang HcySunYang added 🐞 bug Something isn't working 🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. labels Feb 17, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Oct 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. 🐞 bug Something isn't working scope: ssr
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants