[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 The client – side render.

(Note: because this problem is a long time ago, so the problem screenshots are not available, this picture is from my blog above, interested can directly see the blogwww.cnblogs.com/laisiyu/p/1…)

The problem is explained as: “The virtual DOM tree rendered by the client does not match the content rendered by the server. This could be due to incorrect HTML tags, such as nested block-level elements in </p/>, or missing </tbody/>. Drain hydration and perform complete client rendering.”

This means that nesting of elements in your DOM tree, such as putting block-level elements inside inline elements, is against the norm.

There is no element that does not conform to the specification. I checked and found that there is an element that is not acceptable in the element. Instead of deleting it, I annotated it (I will not put pictures here). Then delete the commented code.