Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[1.8] IE11 bug: Unable to get property 'nodeType' of undefined or null reference #4455

Closed
1 of 6 tasks
web-padawan opened this issue Mar 23, 2017 · 3 comments
Closed
1 of 6 tasks

Comments

@web-padawan
Copy link
Contributor

web-padawan commented Mar 23, 2017

Description

This bug happens in IE11 when parsing some pages. Looks like a bug related to elements composition.

SCRIPT5007: TypeError: Unable to get property 'nodeType' of undefined or null reference

The only thing I have right now is the following call stack:

at Polymer.Annotations._parseNodeAnnotations
 at Polymer.Annotations.parseAnnotations
 at Polymer.Annotations._parseTemplate
 at Polymer.Annotations._parseChildNodesAnnotations
 at Polymer.Annotations._parseElementAnnotations
 at Polymer.Annotations._parseNodeAnnotations
 at Polymer.Annotations._parseChildNodesAnnotations
 at Polymer.Annotations._parseElementAnnotations
 at Polymer.Annotations._parseNodeAnnotations
 at Polymer.Annotations._parseChildNodesAnnotations

Steps to Reproduce

I didn't manage to localize this bug yet. Reproducing migh require lots of nested components.
Interestigly the UI doesn't get broken, though. I can see the components and interact with them.

Browsers Affected

  • Chrome
  • Firefox
  • Edge
  • Safari 9
  • Safari 8
  • IE 11

Versions

  • Polymer: v1.8.1
  • webcomponents: v0.7.24
@dfreedm
Copy link
Member

dfreedm commented Mar 23, 2017

Can you provide a link to some example? It is really the only way to help diagnose the issue.

@web-padawan
Copy link
Contributor Author

Seems to be the same as #2682. Will try to create a reduced test case.

@web-padawan
Copy link
Contributor Author

Closing this as no longer relevant. In case someome faces this issue with Polymer 1.x, the problem most likely was in the old version of the template polyfill.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants