Last modified: 2012-09-27 01:14:33 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 12894 - suggestions for modern skin
suggestions for modern skin
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: River Tarnell
Depends on:
  Show dependency treegraph
Reported: 2008-02-03 18:13 UTC by bdk
Modified: 2012-09-27 01:14 UTC (History)
1 user (show)

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


Description bdk 2008-02-03 18:13:26 UTC
Please add the following from monobook/main.css to modern's main.css too (toccolours adapted slightly):

/* emulate center */
.center {
*.center * {

/* table standards */
.toccolours {
    border:1px solid #bbbbbb;

.usermessage is still suboptimal: 
a) If viewed on special pages or on redirects, there are some overlap effects. I didn't find the reason yet.
b) Even if it's not as obtrusive as Monobook's orange bar, it could be a wee bit more eye-catching (some light-blue background perhaps).
Comment 1 River Tarnell 2008-02-03 20:16:08 UTC
i have changed the background colour of the new messages bar to #dadaff.  this is a purplish blue which stands out from the other skin elements without being garish.

the overlap problem on special pages has been fixed (i haven't tested with sitenotice or other decorations at the top of the page)

i added the missing css classes from monobook

(all these changes are in r30490, which i will put live shortly)

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