I'm submitting a bug report
Please tell us about your environment:
-
Operating System:
Windows 10
-
Node Version:
v8.11.3
-
NPM Version:
5.6.0 (but im using yarn anyway)
-
Webpack version
webpack 4.16.0
-
Browser:
Chrome 67
-
Language:
TypeScript 2.9.2
Current behavior:
parent.createChild() doesn't work.
createChild() is not a function.
This only happens with custom elements.
Expected/desired behavior:
buildRowCallback() should parse "<div>test</div>" just like "<some-element></some-element>".
Using <template> around the custom element doesn't work. <template> is set to display: none for some reason.
<some-element> is available as a global resource, so that's not the problem.
- What is the motivation / use case for changing the behavior?
So many possibilities.
I will create a minimum failing example if you want me to.
I'm submitting a bug report
1.0.1
Please tell us about your environment:
Operating System:
Windows 10
Node Version:
v8.11.3
NPM Version:
5.6.0 (but im using yarn anyway)
Webpack version
webpack 4.16.0
Browser:
Chrome 67
Language:
TypeScript 2.9.2
Current behavior:
parent.createChild() doesn't work.
createChild() is not a function.
This only happens with custom elements.
Expected/desired behavior:
buildRowCallback() should parse "<div>test</div>" just like "<some-element></some-element>".Using <template> around the custom element doesn't work. <template> is set to display: none for some reason.<some-element> is available as a global resource, so that's not the problem.So many possibilities.
I will create a minimum failing example if you want me to.