Last modified: 2011-03-13 18:06:12 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T12301, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 10301 - Introduce link syntax to allow for wildcard protocol
Introduce link syntax to allow for wildcard protocol
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-06-18 11:02 UTC by Chris
Modified: 2011-03-13 18:06 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Chris 2007-06-18 11:02:13 UTC
There have been a lot of discussions on adding some specified protocols or not (see Bugs 2807, 3133, 1235, 3147 and related). I would like to make a proposal for a generic solution, as I don't know if this concern has already been solved satisfactorily for everybody.

I would suggest to enhance the syntax of link notation with a generic option.
That would mean to introduce a link notation with three brackets, which doesn't restrict any protocols and is reserved for external links. 
So e.g. [[[sip:me@sipgate.com]]] would generate a link representation to the sip uri. 

So everybody who wants to use an exotic protocol within his link can do it without requesting the wikimaster to add the protocol to $wgUrlProtocols before.
To get it working that way, it would be necessary that everything between the bracktes is considered to be a valid uri with a valid protocol-part / schema. (This is probably the disadvantage of this solution). Beyond this the usual wikisyntax for links could be kept.
Comment 1 Rob Church 2007-06-18 11:13:22 UTC
I'm not keen on introducing a three-bracket link format; brackets are overused as it is.
Comment 2 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-06-18 17:19:21 UTC
We deliberately do not want to allow certain protocols, or so I gather.  See, e.g., bug 4575 comment 3, bug 2807 comment 17.  In the latter case I believe one concern expressed was that clicking the link immediately opened a conversation visible to the recipient and required no further confirmation from the user, or something.
Comment 3 Brion Vibber 2007-06-18 19:12:39 UTC
Insecure and unnecessary.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links