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

Incorrect 'mailto' link scheme #67

Open
jsayol opened this issue Mar 7, 2015 · 1 comment
Open

Incorrect 'mailto' link scheme #67

jsayol opened this issue Mar 7, 2015 · 1 comment

Comments

@jsayol
Copy link

jsayol commented Mar 7, 2015

Bug description

When linking to an email address the URI has to be written as mailto://[email protected] instead of mailto:[email protected]. Only the second form is correct according to the standard.

Expected behaviour

The second form should work as expected and generate the link. Github's Markdown does it correctly.

Steps to reproduce

Write a comment on reddit containing the code

[test](mailto:[email protected])

which should be equivalent to the current

[test](mailto://[email protected])

Proposed fix

Remove the slashes in src/autolink.c to accept 'mailto:'. This will also keep backwards compatibility with the existing 'mailto://' links.

The code over at reddit is already correct.

tryton-vanmeer pushed a commit to tryton-vanmeer/Slide that referenced this issue Apr 24, 2017
ContentType.getContentType returns EXTERNAL for urls that start with 'mailto:'. When LinkUtil.formatURL checks if a url doesn't contain '://', it also makes sure the url doesnt start with 'mailto'.
There still exists an issue with markdown links for mailto as described in this issue -> reddit/snudown#67
@derekantrican
Copy link

There is also a current issue with reddit's mailto:// format. using something like

[link](mailto://[email protected])

will open an email to //[email protected]. Trying to take out those slashes and using

[link](mailto:[email protected])

means the link doesn't render through reddit markdown correctly

@0xN0x 0xN0x mentioned this issue Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants