Skip to content
This repository has been archived by the owner on Apr 11, 2024. It is now read-only.

ES2015 module test fails #502

Closed
WebReflection opened this issue Apr 5, 2017 · 5 comments
Closed

ES2015 module test fails #502

WebReflection opened this issue Apr 5, 2017 · 5 comments

Comments

@WebReflection
Copy link

WebReflection commented Apr 5, 2017

screenshot from 2017-04-05 14-32-02

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.

@NielsLeenheer
Copy link
Collaborator

It doesn't look like you override this behaviour using CSP headers. So loading an external file would be the easiest solution indeed.

@NielsLeenheer
Copy link
Collaborator

Fixed for version 9.0

@WebReflection
Copy link
Author

did such version ship?

I keep seeing a NO under module support

screenshot from 2017-09-20 17-32-09

@WebReflection
Copy link
Author

no answers in moths, closing this to remove it from my issues

@dstorey
Copy link
Contributor

dstorey commented Jan 31, 2018

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.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants