Support Markdown in Add-on Listing Fields #22956
Open
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
chrstinalin
requested review from
a team and
KevinMind
and removed request for
a team
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.
Fixes: mozilla/addons#15145
Description
Replaces HTML syntax support with Markdown support in the
description,developer_comments,eula, andprivacy_policyfields ofAddon. Existing HTML in those fields will remain functional until the field is edited. No new HTML will be functional.Only the markdown-equivalent of currently allowed HTML attributes are allowed.
abbruses the PHP Markdown Extra syntax.DevHub:
Frontend:
Testing
Checklist
#ISSUENUMat the top of your PR to an existing open issue in the mozilla/addons repository.