Last modified: 2010-05-15 15:37:43 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 T9251, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 7251 - A way to see which portlets are due to MediaWiki:Sidebar
A way to see which portlets are due to MediaWiki:Sidebar
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.5.x
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-09-07 01:08 UTC by Andrew Dunbar
Modified: 2010-05-15 15:37 UTC (History)
1 user (show)

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


Attachments

Description Andrew Dunbar 2006-09-07 01:08:42 UTC
I'm writing a JavaScript extension which allows each user to create
User:xyz/MediaWiki:Sidebar to override MediaWiki:Sidebar

On most wikis MediaWiki:Sidebar just defines one portlet named "navigation" but
the syntax allows any number of portlets with any name at all to be defined.
Because there are also any number of portlets before and after those generated
by MediaWiki:Sidebar and those are bound to vary from site to site and version
to version, my extension cannot know in all cases which subset of portlets to
replace.

Possible solution #1:
Wrap all <div class='portlet' id='p-navigation'>-style divs generated by
MediaWiki:Sidebar with something like <div class='sidebar'> or <div id='sidebar'>

Possible solution #2:
Use <div class='portlet sidebar'> for those portlets generated by MediaWiki:Sidebar

#1 is the most straightforward to use by my extension, #2 may seem neater to
some people.
Comment 1 Bryan Tong Minh 2008-03-15 13:45:13 UTC
Added class 'generated-sidebar' in r32016.

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


Navigation
Links