tools: Polymer build --bundle --js-compile not working in ie11
Description
Using Polymer 2.0 and building with polymer --bundle --js-compile is not working in ie11… currently getting the following error
Dug around and saw that template.cloneNode(true) wasn’t cloning the content property, possibly because it was DocumentFragment. Tried doing putting a workaround described in https://github.com/webcomponents/webcomponentsjs/issues/362 but that also yields different errors…
Versions & Environment
- Polymer CLI:1.5.1
- node:v 6.2.0
- Operating System: MacOs 10.11.6
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 21 (13 by maintainers)
We are halfway through our Polymer 2 migration for a large application and running into what I think is this issue. We see it even when we run the polymer shop and the polymer starter kit.
We get an error 1/5 times we load the application, so it seems to be an async issue. The error is random in the form of ‘Unable to get property XXX of undefined or null reference’.
From our debugging, it always happens on this line:
https://github.com/webcomponents/custom-elements/blob/master/src/CustomElementInternals.js#L252
We are in a deadlock now, we need to decide what to do. It would be great to get some official guidance on this.
@usergenic @justinfagnani Any updates or ETA? we’re also planning to use Polymer 2.0 on a new project but won’t be able to if ie11 is not supported…
I am experiencing the exact same error. Tried both webcomponents.js & webcomponents-lite.
Compiling using: