This repository has been archived by the owner on Nov 3, 2021. It is now read-only.
fix bug 863527 by updating test instead of parsing untrusted input (v2) #9326
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
alivedise
added a commit
that referenced
this pull request
Jul 16, 2013
Bug 863527 -- Safer html injection in app error, r=alive
alivedise
added a commit
that referenced
this pull request
Aug 1, 2013
Bug 863527 -- Safer html injection in app error, r=alive (cherry picked from commit fcda94c)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
2nd attempt at fixing bug 863527 - exactly the same as PR #9311 except now without the linter error.
(I broke the last branch while trying to combine commits into one, so it was easier to start a new branch, hence the new PR).