@angular/core 15.2.0-next.3 → 15.2.0-next.4

package/fesm2015/testing.mjs

@@ -1,5 +1,5 @@
 /**
- * @license Angular v15.2.0-next.3
+ * @license Angular v15.2.0-next.4
  * (c) 2010-2022 Google LLC. https://angular.io/
  * License: MIT
  */
@@ -7257,70 +7257,18 @@ class DOMParserHelper {
     }
 }
 /**
- * Use an HTML5 `template` element, if supported, or an inert body element created via
- * `createHtmlDocument` to create and fill an inert DOM element.
+ * Use an HTML5 `template` element to create and fill an inert DOM element.
  * This is the fallback strategy if the browser does not support DOMParser.
  */
 class InertDocumentHelper {
     constructor(defaultDoc) {
         this.defaultDoc = defaultDoc;
         this.inertDocument = this.defaultDoc.implementation.createHTMLDocument('sanitization-inert');
-        if (this.inertDocument.body == null) {
-            // usually there should be only one body element in the document, but IE doesn't have any, so
-            // we need to create one.
-            const inertHtml = this.inertDocument.createElement('html');
-            this.inertDocument.appendChild(inertHtml);
-            const inertBodyElement = this.inertDocument.createElement('body');
-            inertHtml.appendChild(inertBodyElement);
-        }
     }
     getInertBodyElement(html) {
-        // Prefer using <template> element if supported.
         const templateEl = this.inertDocument.createElement('template');
-        if ('content' in templateEl) {
-            templateEl.innerHTML = trustedHTMLFromString(html);
-            return templateEl;
-        }
-        // Note that previously we used to do something like `this.inertDocument.body.innerHTML = html`
-        // and we returned the inert `body` node. This was changed, because IE seems to treat setting
-        // `innerHTML` on an inserted element differently, compared to one that hasn't been inserted
-        // yet. In particular, IE appears to split some of the text into multiple text nodes rather
-        // than keeping them in a single one which ends up messing with Ivy's i18n parsing further
-        // down the line. This has been worked around by creating a new inert `body` and using it as
-        // the root node in which we insert the HTML.
-        const inertBody = this.inertDocument.createElement('body');
-        inertBody.innerHTML = trustedHTMLFromString(html);
-        // Support: IE 11 only
-        // strip custom-namespaced attributes on IE<=11
-        if (this.defaultDoc.documentMode) {
-            this.stripCustomNsAttrs(inertBody);
-        }
-        return inertBody;
-    }
-    /**
-     * When IE11 comes across an unknown namespaced attribute e.g. 'xlink:foo' it adds 'xmlns:ns1'
-     * attribute to declare ns1 namespace and prefixes the attribute with 'ns1' (e.g.
-     * 'ns1:xlink:foo').
-     *
-     * This is undesirable since we don't want to allow any of these custom attributes. This method
-     * strips them all.
-     */
-    stripCustomNsAttrs(el) {
-        const elAttrs = el.attributes;
-        // loop backwards so that we can support removals.
-        for (let i = elAttrs.length - 1; 0 < i; i--) {
-            const attrib = elAttrs.item(i);
-            const attrName = attrib.name;
-            if (attrName === 'xmlns:ns1' || attrName.indexOf('ns1:') === 0) {
-                el.removeAttribute(attrName);
-            }
-        }
-        let childNode = el.firstChild;
-        while (childNode) {
-            if (childNode.nodeType === Node.ELEMENT_NODE)
-                this.stripCustomNsAttrs(childNode);
-            childNode = childNode.nextSibling;
-        }
+        templateEl.innerHTML = trustedHTMLFromString(html);
+        return templateEl;
     }
 }
 /**
@@ -8803,7 +8751,7 @@ class Version {
 /**
  * @publicApi
  */
-const VERSION = new Version('15.2.0-next.3');
+const VERSION = new Version('15.2.0-next.4');
 
 // This default value is when checking the hierarchy for a token.
 //