bug-1918223: fix moz_crash_reason and reason formatting in create bug Description field. #6728
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.
Because:
moz_crash_reason
value (and similarly, thereason
value) was not displaying properly in the Bugzilla create bug page due to some extra whitespace and missing newline characters in the value of thecomment
query parameter passed in the create bug URL.This commit:
Note: Shortly after bug-1919789 was fixed (which temporarily blocked this bug), I can no longer reproduce the issue in this bug locally or in prod, however, it makes sense to make these changes anyway, so that the formatting will reflect standard Markdown formatting regardless of the current Bugzilla create bug URL implementation.
Here's a screenshot of what the Preview looks like in the Bugzilla create bug page with the crash from the ticket (
2827f0eb-4a80-421e-a287-4c77f0240911
) in local development: