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.

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

Ambiguity in <pre> parsing #355

Closed
dikmax opened this issue Aug 2, 2015 · 1 comment
Closed

Ambiguity in <pre> parsing #355

dikmax opened this issue Aug 2, 2015 · 1 comment

Comments

@dikmax
Copy link
Contributor

dikmax commented Aug 2, 2015

By spec line starting with <pre could be parsed using rule 1 or rule 6 which can be ambiguous.
We should define rules precedence or remove 'pre' from tags in rule 6.

@jgm
Copy link
Member

jgm commented Aug 6, 2015

I think 'pre' should be removed from the list in rule 6.
The reference implementations should be updated accordingly.

+++ Maxim Dikun [Aug 02 15 08:50 ]:

By spec line starting with <pre could be parsed using rule 1 or rule 6
which can be ambiguous.
We should define rules precedence or remove 'pre' from tags in rule 6.


Reply to this email directly or [1]view it on GitHub.

References

  1. Ambiguity in <pre> parsing #355

@jgm jgm closed this as completed in bbed621 Aug 8, 2015
jgm added a commit to commonmark/commonmark.js that referenced this issue Aug 8, 2015
jgm added a commit to commonmark/cmark that referenced this issue Aug 8, 2015
See commonmark/commonmark-spec#355. Pre is handled separately in rule 1
and needn't be handled in rule 6.
colinodell added a commit to thephpleague/commonmark that referenced this issue Aug 28, 2015
talum pushed a commit to github/cmark-gfm that referenced this issue Sep 14, 2021
See commonmark/commonmark-spec#355. Pre is handled separately in rule 1
and needn't be handled in rule 6.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants