Files
vscode/build
Matt Bierner 474d4951d8 Switch to dompurify for sanitizing markdown content (#131950)
* Switch to dompurify for sanitizing markdown content

Switches us from using `insane` to instead use `dompurify`, which seems to be better maintained and also has some nice features, such as built-in trusted types support

I've tried to port over our existing sanitizer settings as best as possible, but there's not always a 1:1 mapping between how insane works and how dompurify does. I'd like to get this change in early in the iteration to catch potential regressions

* Remove logging and renaming param

* Move dompurify to browser layer

* Fixing tests and how we check valid attributes

* Allow innerhtml in specific files

* Use isEqualNode instead of checking innerHTML directly

innerHTML can return different results on different browsers. Use `isEqualNode` instead

* Reapply fix for trusted types

* Enable ALLOW_UNKNOWN_PROTOCOLS

I beleive this is required since we allow links to commands and loading images over remote

* in -> of

* Fix check of protocol

* Enable two more safe tags
2021-09-03 12:17:02 -07:00
..
2021-08-31 10:21:19 -04:00
2021-08-17 18:00:32 -07:00
2021-08-20 10:19:59 -07:00
2021-08-12 09:37:55 +02:00
2021-07-19 14:26:16 -07:00
2021-01-07 09:15:05 +01:00
2021-07-09 15:34:36 +02:00
2021-01-25 17:46:09 +01:00
2021-09-02 10:09:25 -07:00
2021-09-02 10:09:25 -07:00