Last modified: 2014-07-15 00:08:56 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 9845 - Special functions of namespaces should not be hardcoded
Special functions of namespaces should not be hardcoded
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Lowest enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on: 9887
  Show dependency treegraph
Reported: 2007-05-08 16:34 UTC by Aryeh Gregor (not reading bugmail, please e-mail directly)
Modified: 2014-07-15 00:08 UTC (History)
3 users (show)

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


Description Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-05-08 16:34:00 UTC
This is a long-term request.  The idea would be, basically, that namespaces like
Image and Category would no longer be magical.  Probably this would be achieved
by something like making an abstract Namespace class that would have functions
like renderLink() and transclude(), so that these could behave differently for
different namespaces.  (These would probably call functions of a Skin object
passed to them.)  Thus Image/Category NSes wouldn't be special-cased in the
parser, but instead it would ask them to render the links and they would do
something appropriate.

Benefits: it's a moderately common request to have other namespaces that behave
like images, etc. (e.g., bug 2194).  This is currently impossible.  It's also
substantially cleaner and possibly more expected to not have special-casing
hardcoded everywhere.  Extensions such as SMW that may want special behavior for
certain namespaces will also have a potentially cleaner way to do it.  Etc. 
Probably not very high-priority, but IMO it would be nice if we did this eventually.
Comment 1 Quim Gil 2013-04-15 16:49:16 UTC
Chad, could you help assessing this old request and whether we might be doing anything about it? Otherwise we should probably assign Lowest priority to reflect the situation so far.
Comment 2 Chad H. 2013-04-15 17:09:56 UTC
Nobody's ever done anything with this. In theory, some of the content handler stuff might've opened the door to making this easier, but the original request (having secondary file or category namespaces) certainly is not possible.
Comment 3 Quim Gil 2014-04-17 05:33:35 UTC
After a year of silence... I'm daring to resolve this request as WONTFIX, as there is no plan or sign of willing to change the attributes currently hardcoded to certain MediaWiki namespaces.
Comment 4 Chad H. 2014-04-17 05:46:06 UTC
Just because nobody's scratched the itch doesn't mean the bug isn't valid. Someone could very well come along and do this.

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