FIX: url escaping on rich editor when autolink/linkify #34164
Merged
+9
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
a3dc356 to
c2c9544
Compare
pento
approved these changes
Aug 8, 2025
|
This pull request has been mentioned on Discourse Meta. There might be relevant details there: |
pento
pushed a commit
that referenced
this pull request
Aug 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the content of the link URL is in the document itself, like in
<https://www.example.com>orwww.example.com, we need to flag it to the serializer so it doesn't try to escape it.ProseMirror's markdown serializer uses
state.inAutoLinkas a signal to avoid this escaping.