Fix Access Denied Errors in IE 11 #43
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix access denied errors in IE 11 when a cross origin frame tries to use getOwnPropertyNames. Apparently IE has a bug where it uses the function defined in the original window.
archangel-irk
added a commit
that referenced
this pull request
Aug 24, 2015
Fix Access Denied Errors in IE 11
|
Thank you very much. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix access denied errors in IE 11 when a cross origin frame tries to use
getOwnPropertyNames. Apparently IE has a bug where it uses the function
defined in the original window.
This is a similar fix as is in an ES6-Shim.
It seemed to address the issue for me. Am using knockout-es5 on Microsoft Office 365 where they create many cross origin iframes.