* Enrich the change event
* Initial tab model building
* Work in progress model construction
* Add pauseable emitter
* Attempt using microtask
* Make tests pass
* Update active tab logic
* Fix layering issue
* event rename
* PR feedback
* Remove stray new line
* Add test for microtask emitter
* Add move event
* Add mmerge functionality to Microtask emitter
* Fix compilation errrors
* Fix tests
* Add tests to address feedback
* Change editor change event to an array
* Add array support to editorsChangeEvent
* Update src/vs/workbench/common/editor/editorGroupModel.ts
Co-authored-by: Benjamin Pasero <benjpas@microsoft.com>
* Switch to a less efficient array method
* Add console.log for debugging
* Test with different notebook
* Fix notebook URI
* For now split up file open for better debugging
* Don't use notebook in test for now
* Cleanup event
* Fix tests
Co-authored-by: Benjamin Pasero <benjamin.pasero@microsoft.com>
Co-authored-by: Benjamin Pasero <benjpas@microsoft.com>
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
