Last modified: 2005-11-20 00:30:52 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 4017 - Invalid CSS generates parsing errors in Firefox
Invalid CSS generates parsing errors in Firefox
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
All All
: Normal minor with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-11-17 20:44 UTC by HorsePunchKid
Modified: 2005-11-20 00:30 UTC (History)
0 users

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


Description HorsePunchKid 2005-11-17 20:44:21 UTC
Originally reported (with lovely wikiformatting and such) at:

There are two problems with the global stylesheet that should be fixed. First,
the filter statement on line 225 should simply be removed: It is nonstandard and
produces errors messages in Firefox. Secondly, the line-height property on line
208 has no units (should be 1.5em, I'm sure), which is invalid and also causes
error messages (but only in the Javascript console).

The global stylesheet I'm referring to is:
Comment 1 Brion Vibber 2005-11-18 04:46:02 UTC
Since this is a local site customization, you should take this to the village pump as mentioned 
on that page.
Comment 2 HorsePunchKid 2005-11-18 19:56:49 UTC
Thanks for the quick response, Brion. I have posted my concern to the talk page
for Common.css. I'll let it sit there for a while and post to the VP if I don't
see any responses.

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