Seems like these syntaxes should work in Remarkup:
[[mailto:chad@phacility.com | Chad Little]]
Maybe should work too?
[Chad Little](mailto:chad@chadsdomain.com)
Description
Description
Revisions and Commits
Revisions and Commits
Related Objects
Related Objects
Event Timeline
Comment Actions
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.
Comment Actions
Dear all, my expectation of mailto: handling was based on mediawiki behavior, where it is correctly interpreted.
Comment Actions
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.
Comment Actions
However this is, as you already mentioned, rather useless, because clicking the link will not allow to send an email
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.