This repository has been archived by the owner on Apr 11, 2024. It is now read-only.
ES2015 module test fails #502
Comments
It doesn't look like you override this behaviour using CSP headers. So loading an external file would be the easiest solution indeed. |
NielsLeenheer
added a commit
that referenced
this issue
May 14, 2017
Fixed for version 9.0 |
no answers in moths, closing this to remove it from my issues |
I know this has been fixed in V9 but Chrome started passing this in V8 and we looked at it and fixed the bug that made it not work, so my thought is the fix should be reverted and use the V8 test so that other browsers fix the bug. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It looks like the only engine that really supports ES2015 modules also has CORS policy enabled by default so that inline eval-scripts are not allowed.
A
try/catch
wouldn't work neither so you rather try to load a./module.js
file with similar logic but a static callback name.The text was updated successfully, but these errors were encountered: