-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: ban version v3.1.7 of DOMPurify #5914
fix: ban version v3.1.7 of DOMPurify #5914
Conversation
[DOMPurify v3.1.7][1] forbids the use of `<foreignElement>` for HTML inside of an `<svg>` element, which breaks many mermaid diagrams. It is likely that v3.1.8 will add a new option that will allow us to re-enable this behaviour, but v3.1.7 definitely does not work. [1]: https://github.com/cure53/DOMPurify/releases/tag/3.1.7 See: cure53/DOMPurify#1002 Fix: mermaid-js#5904
🦋 Changeset detectedLatest commit: de2c05c The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for mermaid-js ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
commit: |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #5914 +/- ##
=======================================
Coverage 5.00% 5.00%
=======================================
Files 337 337
Lines 48209 48209
Branches 576 576
=======================================
Hits 2413 2413
Misses 45796 45796
Flags with carried forward coverage won't be shown. Click here to find out more. |
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
📑 Summary
DOMPurify v3.1.7 forbids the use of
<foreignElement>
for HTML inside of an<svg>
element, which breaks many mermaid diagrams.It is likely that v3.1.8 will add a new option that will allow us to re-enable this behaviour, but v3.1.7 definitely does not work, so we should remove support for it from our
dependencies
.See: cure53/DOMPurify#1002
Resolves #5904
Big thanks to @slorber for their awesome work in communicating with the DOMPurify maintainers (and of course their work on https://docusaurus.io/ 🦖!)
📏 Design Decisions
N/A
📋 Tasks
Make sure you
MERMAID_RELEASE_VERSION
is used for all new features.pnpm changeset
and following the prompts. Changesets that add features should beminor
and those that fix bugs should bepatch
. Please prefix changeset messages withfeat:
,fix:
, orchore:
.