History

Harri Lehtola 12a71bc6bc fix(core): determine required DOMParser feature availability (#36578 ) (#37783 )

Verify that HTML parsing is supported in addition to DOMParser existence.
This maybe wasn't as important before when DOMParser was used just as a
fallback on Firefox, but now that DOMParser is the default choice, we need
to be more accurate.

PR Close #37783

2020-06-29 10:27:39 -07:00

bypass.ts

build: update license headers to reference Google LLC (#37205 )

2020-05-26 14:27:01 -04:00

html_sanitizer.ts

refactor(core): split inert strategies to separate classes (#36578 ) (#37783 )

2020-06-29 10:27:39 -07:00

inert_body.ts

fix(core): determine required DOMParser feature availability (#36578 ) (#37783 )

2020-06-29 10:27:39 -07:00

readme.md

refactor(core): move sanitization into core (#22540 )

2018-03-07 18:24:06 -08:00

sanitization.ts

build: update license headers to reference Google LLC (#37205 )

2020-05-26 14:27:01 -04:00

sanitizer.ts

build: update license headers to reference Google LLC (#37205 )

2020-05-26 14:27:01 -04:00

security.ts

build: update license headers to reference Google LLC (#37205 )

2020-05-26 14:27:01 -04:00

url_sanitizer.ts

build: update license headers to reference Google LLC (#37205 )

2020-05-26 14:27:01 -04:00

readme.md

Sanitization

This folder contains sanitization related code.

History

It used to be that sanitization related code used to be in @angular/platform-browser since it is platform related. While this is true, in practice the compiler schema is permanently tied to the DOM and hence the fact that sanitizer could in theory be replaced is not used in practice.

In order to better support tree shaking we need to be able to refer to the sanitization functions from the Ivy code. For this reason the code has been moved into the @angular/core.