Last modified: 2014-08-19 02:26:41 UTC
This is one of the features mentioned on bug 69550 which are currently implemented by means of a JavaScript hack in common.js of each wiki: https://www.mediawiki.org/wiki/Snippets/Redirect_skin.js A similar redirect should exist for [[Special:MyPage/skin.css]].
I don't think we should make it impossible to create a user subpage literally named "skin.js" or "skin.css". Perhaps a better, more consistent way to do it would be to implement another special page like Special:MyPage that would redirect to the .js/.css user subpage for current skin? I bet someone smart who wants this done can figure it out :)
I think a special page for this is a huge case of over-engineering and would unnecessarily complicate this. Currently English Wikipedia seems to think that User:jdlrobson/skin.js should redirect to the right place. Sure it makes it impossible to create a user subpage called User:Jdlrobson/skin.js but really.. we care about that one single page? :-) I mean.. on English Wikipedia this is pretty much the case already. If you truly do it can be configurable e.g. $wgSkinJavaScriptRedirects and set it to true on English Wikipedia and any other project that wants it.
I like Bartosz idea. I agree that we don't lose much if skin.js isn't accessible anymore, but that's a hack, which means poor quality code and potential problems. A special page can be localized, something that could be more difficult to do with what looks a legitimate subpage. For me, it would require more engineering time to do that hack and be prepared to many unexpected results, some of them that come to my mind without digging too much: * What if that page gets transcluded * Ways to prevent editing that page (through API, through URL manipulation (action=edit) * Ways to prevent any page to be renamed to /skin.js * Existing pages with that name that may exist on the wiki that will become unavailable Also, I think we agree this is an enhancement
Shouldn't we just encourage people to use their common.js/css instead of skin specific ones?
(In reply to Kunal Mehta (Legoktm) from comment #4) > Shouldn't we just encourage people to use their common.js/css instead of > skin specific ones? Yeah, probably.
