Last modified: 2011-11-22 00:26:18 UTC
If we link a page using the full url instead of the internal link syntax, the external link arrow appears next to it. However, in some cases you don't have the choice, like a link to a diff, which has parameters and is tipically something like http://xx.wikipedia.org/w/index.php?param=value¶m?value I think that a choice should be provided by automatically marking links created with {{fullurl}} and similar templates as plainlinks. Also, if that template allowed a parameter for an alias, that would be good . But this probably would be another bug...
*** Bug 17331 has been marked as a duplicate of this bug. ***
{{fullurl}} and similar shouldn't be handles as plainlinks but as normal internal a so the color is the same as internal ones (.plainlinks uses the a.external color). Furthermore links posted like http://mywiki.com or [http://mywiki.com... should be handled the same.
Forgive my naiveness :P -- I don't think I was clear enough back when I originally reported this (and made some mistakes, like assuming that {{fullurl:}} was a template). What I believe should be done is to avoid marking full urls as external links (i.e. add the external arrow) if the domain is the same as {{SERVER}}. It makes sense that the color should be the same as internal links, too.
cf bug 16659, prettify permalinks. Kinda tangentially related.
The title of this bug is confusing (can it be changed?). As posted {{fullurl..., http://mywiki.com or [http://mywiki.com... should be recognized / handled as internal links. Class plainlinks can be removed from the css after this was fixed.
It can be done from Monobook.css but better to do it from the skin to take advantage of $wgServer. It just needs to add: #bodyContent a.external[href ^="{$wgServer}"] { background: none ; padding-right: 0; } (properly escaping $wgServer)
Thinking about this some more, what if we went the following route: 1) Format external links that point internally as internal links (no class, no icons) 2) Leave normal external links as-is 3) Leave .plainlinks in place, it has uses beyond just the external links to internal targets. How does that sound?
1) yeah 2) yeah 3) can't think of any but I'm not that experienced.
3) the current block/ban templates and ip contrib footers use it for whois links and ect
(In reply to comment #7) > Thinking about this some more, what if we went the following route: > > 1) Format external links that point internally as internal links (no class, no > icons) > 2) Leave normal external links as-is > 3) Leave .plainlinks in place, it has uses beyond just the external links to > internal targets. This sounds best. The place to make this decision is during link rendering, before HTML output, *not* in CSS. class="external" but display like an internal link isn't right.
Do we only talk about {{fullurl.. links or is it also possible to recognize "lazy links" like http://mywiki.com or [http://mywiki.com as internal links? Cos most users a too lazy to format a {{fullurl... just to point to some special page using parameters in the URL. It would still be correct for special pages to do so and no need to use {{fullurl... cos no "what links here" etc.
We're talking about anything that uses [http://mywiki.com ...], whether that's generated from {{fullurl}} or typed out by hand or assembled by voodoo magic. The external link processor doesn't know or care about templates or magic words, it runs after those have all been substituted to wikitext. It could also apply to bare links like just "http://mywiki.com".
*** Bug 11124 has been marked as a duplicate of this bug. ***
*** Bug 19249 has been marked as a duplicate of this bug. ***
This bug is related: https://bugzilla.wikimedia.org/show_bug.cgi?id=30883
*** Bug 30883 has been marked as a duplicate of this bug. ***
