Describe the bug
According to Vuetify's documentation for <v-tabs-items>, they used null as the initial value for v-model of this component. But if we use null for it, the generated SSR code is all comments <!---->, but on the client side is correct. This mismatch in nodes, causes the well known DOMException: Failed to execute 'appendChild' on 'Node': This node type does not support this method.. Although if you use 0 as the initial value of v-model, it does not occur.
NOTE: This behavior only happens when you run npm run build && npm start and dose not happen when running the development version using npm run dev.
Module version
^1.12.3
Describe the bug According to Vuetify's documentation for
<v-tabs-items>
, they usednull
as the initial value forv-model
of this component. But if we usenull
for it, the generated SSR code is all comments<!---->
, but on the client side is correct. This mismatch in nodes, causes the well knownDOMException: Failed to execute 'appendChild' on 'Node': This node type does not support this method.
. Although if you use0
as the initial value ofv-model
, it does not occur.NOTE: This behavior only happens when you run
npm run build && npm start
and dose not happen when running the development version usingnpm run dev
.To Reproduce https://codesandbox.io/s/v-tabs-items-bug-with-null-v-model-olnx21?file=/pages/index.vue
Steps to reproduce the behavior:
<v-tabs-items>
component with few<v-tab-item>
children and assign it'sv-model
to a data variable.null
npm run build && npm start
DOMException: Failed to execute 'appendChild' on 'Node': This node type does not support this method.
Expected behavior Have the same behavior in both server and client.
Screenshots![Screen Shot 2022-03-23 at 8 03 33 PM](https://user-images.githubusercontent.com/21037809/159736973-11f8506e-9dfe-4106-9bef-ad9ba28def89.png)