mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
980f6a4958
In Chrome 83 passing a TrustedScript to eval just returns the
TrustedScript back without evaluating it, causing the
newTrustedFunctionFor{Dev,JIT} functions to fail. This is a browser bug
that has been fixed in Chrome 84, and only affects Angular applications
running with JIT (which includes unit tests).
As a temporary workaround for users still on Chrome 83, detect when this
occurs in the newTrustedFunctionFor* functions and fall back to the
straightforward, non-Trusted Types compatible implementation. The only
combination that is left affected consists of Angular applications
running with JIT, that have explicitly configured Trusted Types in
enforcement mode, with users that are still on Chrome 83.
Also correct docstring for newTrustedFunctionForJIT.
PR Close #40815
|
||
|---|---|---|
| .. | ||
| abstract_emitter.ts | ||
| abstract_js_emitter.ts | ||
| js_emitter.ts | ||
| map_util.ts | ||
| output_ast.ts | ||
| output_interpreter.ts | ||
| output_jit.ts | ||
| output_jit_trusted_types.ts | ||
| source_map.ts | ||
| ts_emitter.ts | ||
| value_util.ts | ||