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

Apply style on email address will break email parsing/link #288

Closed
PeterDaveHello opened this issue Dec 19, 2016 · 2 comments
Closed

Apply style on email address will break email parsing/link #288

PeterDaveHello opened this issue Dec 19, 2016 · 2 comments
Labels
upstream This issue belongs to a library or component outside

Comments

@PeterDaveHello
Copy link
Contributor

PeterDaveHello commented Dec 19, 2016

Style on email address will break the email parsing and then generate wrong link on the email, examples:

 - **peter**@peter.com
 - **peter**.rd@peter.com
 - peter**.rd**@peter.com
 - peter@**peter.com**
@ccoenen
Copy link
Contributor

ccoenen commented Dec 28, 2016

Id vote to close this unresolved. It's an edge-case that can be worked around quite easily with the long form of the links:

 - **peter**@peter.com -> [**peter**@peter.com](mailto:peter@peter.com)
 - **peter**.rd@peter.com -> [**peter**.rd@peter.com](mailto:peter.rd@peter.com)
 - peter**.rd**@peter.com -> no solution, see below
 - peter@**peter.com** -> [peter@**peter.com**](mailto:peter@peter.com)

The behaviour is also the same on Githubs Markdown (output of exactly the code above):

a) I find this to be a rare case
b) finding and parsing this level of intertwined formatting address is a can of worms
c) there's a valid workaround that is unambiguous to parse and display
d) formatting within an email address is not part of the markdown standard
e) example three does not work at all with other examples as well: (enclosed**.bold**text with a dot as first character)

@jackycute jackycute added the upstream This issue belongs to a library or component outside label Feb 27, 2017
@jackycute
Copy link
Member

This definitely is a edge case and I don't think will be fixed in markdown-it because this is not in the spec.
Please avoid this kind of usage.
Thanks for testing @ccoenen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream This issue belongs to a library or component outside
Projects
None yet
Development

No branches or pull requests

3 participants