Fix: Issue 1785 - IE11 - Requiring mixed content never resolves or errors #1786
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.
#1785
Websites served over HTTPS will refuse to load HTTP urls by default.
While all browsers reject an attempt to require([ 'http://some/module' ]), the timing is different on IE.
IE throws an error when adding the node.src attribute
Other browsers error out when appending the node to the DOM.
In the Chrome/FF/Safari/etc... scenario, the error callback is triggered and the error is reported.
For IE, the script tags are never a part of the DOM and the callbacks for load or error are not invoked. The result is an unhandled exception coming from requirejs and the calling code is never notified of the failure.
The Fix
Try/Catch around the action of adding the node.src, and notify the caller of the script error.