You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
The problem is, that $compile, jqLite and built-in directives like ngInclude always create DOM elements (from HTML strings) in the document of the page where angular is loaded and not the document the nodes were added to. Some browsers, like Internet Explorer don't support adding nodes from a different document.
$compile should use the owner document of the given node and compile the rest in the context of this document.
jqLite should support a second argument for owner document like jQuery.
Built-in directives should use owner document of directive node
The text was updated successfully, but these errors were encountered:
I want to use angular.js in a project for a web portal (Microsoft SharePoint). The requirement is to use the default UI components whenever possible. The native UI provides an API for opening modal dialog windows with an HTML element as content. Content is rendered in an iframe by the system. I want to expand the angular app of the parent page also to the modal window.
When adding angular elements to other frames or windows dynamically using $compile service a HierarchyRequestError is thrown in Internet Explorer.
Here is a simple example that demonstrates the issue:
http://plnkr.co/edit/47PFR8bJ7H58yHBmaX5S?p=preview
The problem is, that $compile, jqLite and built-in directives like ngInclude always create DOM elements (from HTML strings) in the document of the page where angular is loaded and not the document the nodes were added to. Some browsers, like Internet Explorer don't support adding nodes from a different document.
The text was updated successfully, but these errors were encountered: