Last modified: 2014-10-15 23:53:30 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 T53076, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 51076 - GettingStarted toolbar breaks Monobook top tabs
GettingStarted toolbar breaks Monobook top tabs
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
GettingStarted (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-09 22:41 UTC by Matthew Flaschen
Modified: 2014-10-15 23:53 UTC (History)
5 users (show)

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


Attachments
Screenshot (310.98 KB, image/png)
2013-07-11 00:09 UTC, Steven Walling
Details

Description Matthew Flaschen 2013-07-09 22:41:00 UTC
The GettingStarted toolbar is broken in Monobook.  In both Firefox (21) and Chrome (25), it obscures the top tabs, so they show as empty white rectangles.  In Chrome, both the font and white rectangles (tabs) are also very small.
Comment 1 Steven Walling 2013-07-11 00:09:06 UTC
Created attachment 12823 [details]
Screenshot
Comment 2 Steven Walling 2013-07-11 00:09:36 UTC
In addition to breaking the top tabs, the font size is way too small.
Comment 3 Matthew Flaschen 2014-10-15 23:53:30 UTC
Cause suggested by Redrose64:

"This is MonoBook skin, and it appears from examining the HTML of a typical page that the <div id="column-content">...</div> is displaced downwards by an appropriate amount, but the <div id="column-one">...</div> is not. It is that second div that contains the tabs, also the links for user page, user talk page, watchlist, contribs etc. so all of these become hidden."

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


Navigation
Links