IE9 throws "SCRIPT1014: Invalid character"
See original GitHub issueIE9 throws “SCRIPT1014: Invalid character”, despite page charset being set to UTF-8.
The issue is coming from the ` in the following line 352, index.js: return new Function(params, “return `”+literal+“`;”);
Just needs changing to:
return new Function(params, "return '"+literal+"';");
Will raise a pull request to fix.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
IE11 throwing "SCRIPT1014: invalid character" where all other ...
Here's a new one, IE11 is throwing errors on code that works in every other browser. Anyway, after a few hours of "fixing"...
Read more >SCRIPT1014 : Invalid character - Internet explorer 11
Did anyone encounter this issue in IE11 or got a solution for the error - SCRIPT1014 : Invalid character on executing javascript on...
Read more >AngularJS Yeoman + Grunt Build Script1014 Invalid Character ...
Coding example for the question AngularJS Yeoman + Grunt Build Script1014 Invalid Character IE9-grunt.js.
Read more >Google Code Archive - Google Code
IE9 often reports in the console: SCRIPT1014: Invalid character runner.js, line 356 character 31684. IE will also throw Method Access exception in some ......
Read more >jQuery : IE11 throwing "SCRIPT1014: invalid character" where ...
jQuery : IE11 throwing " SCRIPT1014 : invalid character " where all other browsers work [ Beautify Your Computer ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
0.3.2
version published with support for IE 9/10/11 by replacing template string literal logic with simple string manipulation. The changes are published as v0.3.2 - https://www.npmjs.com/package/react-d3-speedometer with all tests passing.Feel free to reopen this issue if you find any problems with IE with the latest release
v0.3.2
. Thank you once again for raising this issue and suggesting the fix for supporting IE.Great, thanks Arun - that means I can now consume react-d3-speedometer directly. Will attempt to resolve any subsequent issues via pre-tested(!) pull request.