Last modified: 2009-01-24 01:17:47 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 15997 - Border on monobook is black and incomplete
Border on monobook is black and incomplete
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-15 22:13 UTC by Mike.lifeguard
Modified: 2009-01-24 01:17 UTC (History)
0 users

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


Attachments
skin strangeness (16.36 KB, image/png)
2008-10-15 22:13 UTC, Mike.lifeguard
Details

Description Mike.lifeguard 2008-10-15 22:13:45 UTC
Created attachment 5440 [details]
skin strangeness

Kindof a strange thing to explain in text, so I've attached a screenshot. This might be a bug in FF3, but it's highly inconsistent, or maybe MediaWiki and FF aren't playing nice. The border will randomly fix itself, and is often fine. When it's not, it's black (supposed to be grey), and simply stops partway down the page. Dunno what other info will be useful, so just ask.

Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Comment 1 Mike.lifeguard 2009-01-24 01:17:47 UTC
This was a bug in my browser since upgrading fixed it I guess. -> INVALID

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


Navigation
Links