Let HTML.escape only escape &<>"' #5012
Merged
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.
Fixes #3233
According to OWSAP these are the only ones that should be escaped. Well, actually, they also recommend escaping
/
. However, Ruby, Python and Go just escape these, so I think it's pretty safe if we do the same thing.About
unescape
: maybe more (all) named chars should be unescaped, but it's out of the scope of this PR.This basically undoes #2175, which was a mistake.