-
Notifications
You must be signed in to change notification settings - Fork 201
Framing fails in IE11 and Edge with "Invalid calling object" #319
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
Comments
thanks for this one. if the issue just consists of adding window to setImmediate you could probably just submit a PR for it. |
Hi @aljones15, thanks for a quick reply. I tried to replace
And this change fixes the issue in Edge. Unfortunately it still fails in IE, now with this error:
I think the syntax error is caused by ES6+ syntax in Should |
Have you tried a polyfil? https://github.com/YuzuJS/setImmediate I'm a bit surprised we don't use one. Thanks for the update. |
It will probably work with polyfill in Edge but at the same time won't solve syntax error from |
|
@dlongley |
Uh oh!
There was an error while loading. Please reload this page.
In IE11 framing fails at
setImmediate()
call, probably due to an Internet Explorer-specific bug which requiressetImmediate()
to be called only onwindow
context.There is already a check related to this issue for IE10 but it doesn't work on IE11 because it defines
setImmediate
function:https://github.com/digitalbazaar/jsonld.js/blob/master/lib/util.js#L37
EDIT: It also fails in Edge for the same reason.
The text was updated successfully, but these errors were encountered: