Fix ampersand HTML escape in dropdown #3205
Draft
+55
−102
Conversation
This file contains 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
auto-assign
bot
requested review from
ColinFrick,
ko2in,
lubber-de,
prudho and
y0hami
mvorisek
changed the title
mvorisek
commented
Mar 10, 2025
| @@ -3838,24 +3838,21 @@ | |||
|
|
|||
| return text.replace(regExp.escape, '\\$&'); | |||
| }, | |||
| htmlEntities: function (string, forceAmpersand) { | |||
| forceAmpersand = typeof forceAmpersand === 'number' ? false : forceAmpersand; | |||
| htmlEntities: function (string) { | |||
There was a problem hiding this comment.
IDK why forceAmpersand was introduced in #2705. What is the usecase when ampersand "must not be escaped to make things safe"?
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.
fix #3199 (comment)
also escape
&, relying on special escape grammar can be dangerous