-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Internet Explorer 11 "Failed to open data:text/javascript;charset=utf-8," #1485
Comments
This was not what I thought it was, simple project structure. |
I also have the same issue. |
👍 Same here |
OK, Yikes, this was a while ago. The first thing I would do is make sure that your template structures are not to complex (caveat we are running on Polymer 0.5, we are upgrading soon ), We found that on 0.5 deeply nested templates can cause issues, in-line as much as possible on those. We also provided id params on any custom elements, so the element:
So I'd start by looking at your templates, hence my cryptic previous comment. Make sure you are using the webcomponent tester and associated testing tools, found on the Polymer blog. I'm very sorry I can't be more specific, as it was a while ago. I will reply back if I remember anymore |
Also started experiencing this on IE11 |
Heh, I bumped into this again and to my surprise, I found myself in this issue. For future reference, if I bump into myself for a third time:
Workaround: stay away from https://ariya.io/2013/02/es6-and-object-literal-property-value-shorthand even if you are running a shiv for IE11. |
Got the same issue on Polymer will checkout the web component tester... |
Found the related Polymer loading issue (for my issue at least). It still renders poorly as UTF8 in IE though for other errors... |
Hi all,
we have a component in our Polymer project that is returning URL encoding, in the debugger it shows as:
We are importing this file through a
This files registers a polymer element name in the file itself:
And includes this as a component as .
This works really well for all browsers apart from IE which seems to barf the encoding of the file....
I'm using master branch, some of the components are to version 0.6.1
Any suggestions?
The text was updated successfully, but these errors were encountered: