Current nightly has issues with intl: https://github.com/microsoft/TypeScript/issues/45804
The previous nightly seems to have some regression around types that cause a build failure
Just go back to last known good build for now
* 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
* initial move to worker
* move event handling to the untitledTextEditorModel
* reuse simpleWorker interfaces and classes
* use correct path to languageDetection
* have vscode-languagedetection be outside of the asar
* add telemetry
* don't unpackage anything from languagedetection because it's not needed
* add an integration test
* some of Ben's feedback
* rework worker code to avoid duplication
* add isDisposed check
* fix test
* Isi and Ben feedback part 2
* use RunOnceScheduler instead and try to fix the test using events
* Ben feedback part 3
* bump distro
* fix: use clang and libcxx from chromium
* chore: add flags for Link-Time Optimization
libcxx builds from upstream are built with LTO, avoiding these
flags will cause miscompiles
* chore: add lto flags to compilation units