fix(ivy): ensure that the correct document
is available (#33712)
Most of the use of `document` in the framework is within the DI so they just inject the `DOCUMENT` token and are done. Ivy is special because it does not rely upon the DI and must get hold of the document some other way. There are a limited number of places relevant to ivy that currently consume a global document object. The solution is modelled on the `LOCALE_ID` approach, which has `getLocaleId()` and `setLocaleId()` top-level functions for ivy (see `core/src/render3/i18n.ts`). In the rest of Angular (i.e. using DI) the `LOCALE_ID` token has a provider that also calls setLocaleId() to ensure that ivy has the same value. This commit defines `getDocument()` and `setDocument() `top-level functions for ivy. Wherever ivy needs the global `document`, it calls `getDocument()` instead. Each of the platforms (e.g. Browser, Server, WebWorker) have providers for `DOCUMENT`. In each of those providers they also call `setDocument()` accordingly. Fixes #33651 PR Close #33712
This commit is contained in:

committed by
Kara Erickson

parent
5b292bf125
commit
83626962cf
@ -6,6 +6,7 @@
|
||||
* found in the LICENSE file at https://angular.io/license
|
||||
*/
|
||||
|
||||
import {getDocument} from '../render3/interfaces/document';
|
||||
import {SANITIZER} from '../render3/interfaces/view';
|
||||
import {getLView} from '../render3/state';
|
||||
import {renderStringify} from '../render3/util/misc_utils';
|
||||
@ -42,7 +43,7 @@ export function ɵɵsanitizeHtml(unsafeHtml: any): string {
|
||||
if (allowSanitizationBypassAndThrow(unsafeHtml, BypassType.Html)) {
|
||||
return unwrapSafeValue(unsafeHtml);
|
||||
}
|
||||
return _sanitizeHtml(document, renderStringify(unsafeHtml));
|
||||
return _sanitizeHtml(getDocument(), renderStringify(unsafeHtml));
|
||||
}
|
||||
|
||||
/**
|
||||
|
Reference in New Issue
Block a user