Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix for ampersands in markdown #1174

Merged
merged 1 commit into from May 2, 2017
Merged

Fix for ampersands in markdown #1174

merged 1 commit into from May 2, 2017

Conversation

nickevansuk
Copy link
Contributor

I believe this same issue still exists for ampersands

@nickevansuk
Fix for ampersands in markdown
3e4e45f 
The same issue exists for ampersands
@marcoscaceres
Copy link
Member

@nickevansuk, this looks good! Could you provide me with an example of what it is effecting? I'd like to add a test for it, at least to check that we don't regress this in the future.

@marcoscaceres marcoscaceres self-requested a review March 30, 2017 10:07
@marcoscaceres marcoscaceres merged commit 9502017 into w3c:develop May 2, 2017
marcoscaceres added a commit that referenced this pull request May 3, 2017
@marcoscaceres
Merge branch 'develop' into gh-pages
31847ac 
* develop:
  v11.4.4
  fix(core/markdown): allow ampersands in markdown (#1174)
  refactor(templates/sotd): only request comments on wgPublicList if it exists (#1195)
@nickevansuk nickevansuk mentioned this pull request Jul 25, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@marcoscaceres marcoscaceres Awaiting requested review from marcoscaceres

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@nickevansuk @marcoscaceres