Page MenuHomePhabricator

Read access to skins files within the wiki
Closed, InvalidPublic

Description

I've spent most of the past year travelling through Central America without a
computer yet I've successfully been developing enhancements to the English
Wiktionary using CSS and JavaScript. It is often not easy or even impossible to
see the CSS and JavaScript files used by skinds such as monobook yet it is often
essential to see how they work to develop such enhancements.

We already have:

MediaWiki:Common.css
MediaWiki:Monobook.css
User:Hippietrail/monobook.css
(and matching .js files)

but not these:

skins-1.5/monobook/main.css
skins-1.5/common/commonPrint.css
skins-1.5/monobook/IE50Fixes.css
skins-1.5/monobook/IE55Fixes.css
skins-1.5/monobook/IE60Fixes.css
skins-1.5/monobook/IE70Fixes.css
skins-1.5/common/IEFixes.js

The main difference is these files will not be editable but the edit tab could
become the "View source" tab as when a non-sysop tries to edit a protected page.


Version: unspecified
Severity: enhancement

Details

Reference
bz6155

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 9:19 PM
bzimport set Reference to bz6155.
bzimport added a subscriber: Unknown Object (MLST).

robchur wrote:

I would assume that those developing such enhancements could access the
Subversion repo to check out the latest skin files, including templates and CSS.

This bug could set a precedent of allowing access to bits of the MediaWiki code
itself through the wiki, which might sound all futuristic and "cool" and nice
and what have we, but it starts to add to the clutter. We'd need a new means of
addressing such content title-wise; new link syntaxes, etc.

These files are all visible. Pop them in your URL bar or use a browser that lets you
conveniently link to them from a view-info box.