-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
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
vue-server-renderer: <hello will cause Server/Client DOM mismatch #6345
Comments
Please follow the Issue Reporting Guidelines and provide a minimal JSFiddle or Github repository containing a set of reproducible steps that can lead to the behaviour you described. Make sure to boil down the problem as much as possible. Thanks! |
Here is a simple repo using nuxt (other ssr frameworks, eg. ream, have the same issue, so pretty convinced it's a vue-ssr bug) |
It would help if you make it with vanilla Vue, thanks |
I've nailed this issue down to I don't know why this would be necessary, since browsers do this anyway. Adding |
Thanks for the concise repro. Looks like a bug. Thanks for proposing a PR |
Version
2.4.2
Reproduction link
https://jsfiddle.net/50wL7mdz/52896/
Steps to reproduce
Just make an SSR app using nuxt or something else and put
<hello
into the template.What is expected?
No error
What is actually happening?
Console output:
[Vue warn]: The client-side rendered virtual DOM tree is not matching server-rendered content. This is likely caused by incorrect HTML markup, for example nesting block-level elements inside <p>, or missing <tbody>. Bailing hydration and performing full client-side render.
The text was updated successfully, but these errors were encountered: