Page MenuHomePhabricator
Create Task
Maniphest T3949

Support mailto URI in Remarkup
Closed, ResolvedPublic
Actions

Description

Seems like these syntaxes should work in Remarkup:

[[mailto:chad@phacility.com | Chad Little]]

Maybe should work too?

[Chad Little](mailto:chad@chadsdomain.com)

Revisions and Commits

Restricted Differential RevisionRestricted Diffusion Commit
Restricted Differential RevisionRestricted Diffusion Commit

Event Timeline

chad created this task.Oct 13 2013, 3:46 AM
chad raised the priority of this task from to Needs Triage.
chad updated the task description. (Show Details)
chad added a project: Remarkup.
chad updated the task description. (Show Details)
chad added subscribers: chad, epriestley, btrahan.
maemarcus added a subscriber: maemarcus.Oct 13 2013, 3:48 AM
epriestley added a comment.Oct 13 2013, 11:35 AM

For all HTTP-like protocols (e.g., ftp), you can configure this by setting uri.allowed-protocols. You can add mailto there, too, but we assume protocols have the form proto://, not proto:, so only links like mailto://a@b.com will get linked. These don't work, because they try to send mail to literally //a@b.com

Allowing mailto: means special casing several levels of the parser. I don't think this opens up any new ground for us, since the only other protocol I can think of which behaves like this is javascript:, and we can never allow that.

I'm also not sure how broadly useful this feature is.

epriestley triaged this task as Wishlist priority.Oct 13 2013, 11:35 AM
maemarcus added a comment.Oct 15 2013, 3:07 PM

Dear all, my expectation of mailto: handling was based on mediawiki behavior, where it is correctly interpreted.

epriestley edited this Maniphest Task.May 3 2014, 1:58 AM
epriestley edited this Maniphest Task.
epriestley edited this Maniphest Task.May 4 2014, 5:47 PM
epriestley edited this Maniphest Task.
epriestley closed this task as Resolved.May 4 2014, 5:48 PM

Closed by commit rP58fbb0ae532f.

devurandom added a subscriber: devurandom.Jul 7 2015, 7:31 AM
devurandom reopened this task as Open.EditedJul 7 2015, 7:45 AM

As I see it, rP58fbb0ae532f implements parsing of mailto://. However this is, as you already mentioned, rather useless, because clicking the link will not allow to send an email (in KMail, it opens a new-mail window with an empty To: field). Is it possible to reconsider fixing this in a way that actually works?

Regarding your concern about no other protocols existing that would use the same scheme: RFC5341 defines the tel: scheme. There also exist doi:, sip:, skype:, xmpp:, bitcoin:, geo: (which actually can be observed in the wild) and others (which are less common).

Regarding rendering I propose to not output the protocol: prefix - i.e. render "tel:+1234" as "+1234" and include "tel:" only in the href.

epriestley closed this task as Resolved.Jul 7 2015, 12:31 PM
epriestley claimed this task.

However this is, as you already mentioned, rather useless, because clicking the link will not allow to send an email

it-works@fine-after-D8963.com

Screen Shot 2015-07-07 at 5.29.41 AM.png (1×1 px, 75 KB)

Regarding your concern about no other protocols existing that would use the same scheme: RFC5341 defines the tel: scheme. There also exist doi:, sip:, skype:, xmpp:, bitcoin:, geo: (which actually can be observed in the wild) and others (which are less common).
Regarding rendering I propose to not output the protocol: prefix - i.e. render "tel:+1234" as "+1234" and include "tel:" only in the href.

We're satisfied with the current behavior and support. You can use [[ a | b ]] to change the title.

urzds added a subscriber: urzds.Jul 12 2017, 11:16 AM
Herald added a subscriber: eadler. · View Herald TranscriptJul 12 2017, 11:16 AM
Phabricator · Built by Phacility