Miško Hevery 2e4d17f3a9 perf(core): make sanitization tree-shakable in Ivy mode (#31934) ... In VE the `Sanitizer` is always available in `BrowserModule` because the VE retrieves it using injection. In Ivy the injection is optional and we have instructions instead of component definition arrays. The implication of this is that in Ivy the instructions can pull in the sanitizer only when they are working with a property which is known to be unsafe. Because the Injection is optional this works even if no Sanitizer is present. So in Ivy we first use the sanitizer which is pulled in by the instruction, unless one is available through the `Injector` then we use that one instead. This PR does few things: 1) It makes `Sanitizer` optional in Ivy. 2) It makes `DomSanitizer` tree shakable. 3) It aligns the semantics of Ivy `Sanitizer` with that of the Ivy sanitization rules. 4) It refactors `DomSanitizer` to use same functions as Ivy sanitization for consistency. PR Close #31934		2019-08-15 10:30:12 -07:00
..
browser	perf(core): make sanitization tree-shakable in Ivy mode (#31934)	2019-08-15 10:30:12 -07:00
dom	test(platform-browser): fix shadow dom test not working in firefox 65 (#29518)	2019-03-26 10:40:25 -07:00
security	test(ivy): enable ivy tests for platform-browser (#27460)	2018-12-04 20:02:33 -08:00
static_assets	refactor: move angular source to /packages rather than modules/@angular	2017-03-08 16:29:27 -08:00
BUILD.bazel	build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871)	2019-02-28 12:06:36 -08:00
browser_util_spec.ts	build: remove `main()` from specs (#21053)	2017-12-22 13:10:51 -08:00
testing_public_spec.ts	refactor: fix typescript strict flag failures in all tests (#30993)	2019-07-18 14:21:26 -07:00