<h3 dir="auto">Version</h3>
<p dir="auto">2.5.16</p>
<h3 dir="auto">Reproduction link</h3>
<p dir="auto"><a href="https://codepen.io/dengdan99/pen/qwEGmg?editors=1111" rel="nofollow">https://codepen.io/dengdan99/pen/qwEGmg?editors=1111</a></p>
<h3 dir="auto">Steps to reproduce</h3>
<p dir="auto">子组件（child）被销毁并重新创建了，</p>
<h3 dir="auto">What is expected?</h3>
<p dir="auto">子组件不被销毁</p>
<h3 dir="auto">What is actually happening?</h3>
<p dir="auto">子组件被销毁并重新挂载</p>
<h3 dir="auto">Version</h3>
<p dir="auto">2.6.10</p>
<h3 dir="auto">Reproduction link</h3>
<p dir="auto"><a href="https://github.com/MKRazz/vue-boolean-prop-issue">https://github.com/MKRazz/vue-boolean-prop-issue</a></p>
<h3 dir="auto">Steps to reproduce</h3>
<ol dir="auto">
<li>Create a component with a boolean property, pass the value of empty string to that property.</li>
<li>Render the value, shows as empty string, rather than false</li>
</ol>
<h3 dir="auto">What is expected?</h3>
<p dir="auto">Since the property is set to type boolean the result to should be treated as such.</p>
<h3 dir="auto">What is actually happening?</h3>
<p dir="auto">Components which have a boolean property aren't able to assert that it is actually a boolean.</p>
<hr>
<p dir="auto">I know there is already <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="200732487" data-permission-text="Title is private" data-url="https://github.com/vuejs/vue/issues/4710" data-hovercard-type="issue" data-hovercard-url="/vuejs/vue/issues/4710/hovercard" href="https://github.com/vuejs/vue/issues/4710">#4710</a>, which was answered. And I can partially agree with that, however this case is slightly different:</p>
<ul dir="auto">
<li>Consider dynamic bindings <code class="notranslate">:prop="''"</code> instead of <code class="notranslate">prop=""</code></li>
<li>Every implementer of vue would need to explicitly coerce the input to a boolean to prevent propagating this problem.</li>
<li>I want to make sure that the data in vue isn't blindly being passed to the html element, and we need to fix this somewhere.</li>
</ul>