<h3 dir="auto">Version 2.6.7 on my computer, not sure about the version used in jsfiddle</h3>
<h3 dir="auto">Reproduction link</h3>
<p dir="auto"><a href="https://jsfiddle.net/cicsolutions/qkzjp520/6/" rel="nofollow">https://jsfiddle.net/cicsolutions/qkzjp520/6/</a></p>
<h3 dir="auto">Steps to reproduce</h3>
<p dir="auto">Create three named slots: (1) with no dash in the slot name, like 'header' or 'footer', as in the docs. (2) with a dash in the name, like 'card-header' and (3) with a camelCased slot name.</p>
<p dir="auto">Console log the slot contents at the created and mounted hooks (other lifecycle hooks not tested) of the component.</p>
<h3 dir="auto">What is expected?</h3>
<p dir="auto">I would expect the slot contents for all slot name syntaxes to be available at in the lifecycle hooks and rendered in component. (unsure if hyphenated or camelCasing is preferred for compound names)</p>
<p dir="auto">I would 100% expect that if the contents of the slot can be logged to the console during created/mounted hooks, that it could be rendered via the render function (which appears to not be true for camelCased slot names)</p>
<h3 dir="auto">What is actually happening?</h3>
<p dir="auto">The slot content for a slot where the name contains a dash is undefined at the created hook, whereas the slot content where the name does not have a dash is defined as expected with the slot node object.</p>
<p dir="auto">Most strange ... content for the slot with a camelCased name is logged to the console properly, but not rendered in the component.</p>
<hr>
<p dir="auto">Please let me know if this type of report is unhelpful.  I really don't have the time to first search the forums and such, and I'm still learning Vue, so I'm unsure if for some reason this would be intended behavior.</p>
<p dir="auto">I do not see anything in the docs that gives notes about the syntax for the slot names that may be compound phrases/names.  However I thought I read somewhere in the docs that camelCase is not valid HTML, so i first figured the hyphenated version of the slot name would be correct.</p>
<p dir="auto">It does make sense to me that the value that follows the colon in the directive declaration becomes the $slots object key, and the value is not rendered as a DOM element attribute, so I thought perhaps using camelCase is the proper way to have compound slot names.  But when using camelCase slot names, the slot content does appear in the console, but is not rendered via the render function.  So ... that's even stranger!?</p>
<p dir="auto">It would be great if the docs could touch on the proper naming convention for slot names, as compound slot names seem like they would be a pretty common approach to slot naming.</p>
<p dir="auto">Note: I did not test other lifecycle hooks.</p>
<p dir="auto">Perhaps I'm not understanding slots properly, but it seems strange to me that a slot named with a dash will render properly but show as undefined for in the created/mounted hooks.  And the opposite: having a camelCase slot name does show a correct node value in the hooks, however does not actually render the slotted content.</p>
<p dir="auto">Hope this helps!  Thanks so much for all you do!  Vue is simply the best framework I've ever used!</p>
<h3 dir="auto">Version</h3>
<p dir="auto">2.5.13</p>
<h3 dir="auto">Reproduction link</h3>
<p dir="auto"><a href="https://codesandbox.io/s/6yk5o1x573" rel="nofollow">https://codesandbox.io/s/6yk5o1x573</a></p>
<h3 dir="auto">Steps to reproduce</h3>
<p dir="auto">In parent component, apply a scoped class to a div. In the child, name the class the same and make sure it's scoped, but use different CSS properties so there's no overwriting.</p>
<h3 dir="auto">What is expected?</h3>
<p dir="auto">I would expect scoped classes to actually be scoped.</p>
<h3 dir="auto">What is actually happening?</h3>
<p dir="auto">Scoped styles are leaking into the children. The divs are sharing 'data-v' attributes which is very bad.</p>