Last modified: 2010-05-15 15:38:00 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 4264 - CSS class is stripped from PRE elements
CSS class is stripped from PRE elements
Status: RESOLVED DUPLICATE of bug 3935
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
PC Linux
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-12-13 07:00 UTC by mediawiki
Modified: 2010-05-15 15:38 UTC (History)
0 users

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


Description mediawiki 2005-12-13 07:00:17 UTC
Styling is stripped from "<PRE>" elements when rendered.  

I've tried to create a special CSS style to use to show code or commands entered
on a screen.  In MediaWiki:Monobook.css, I've added the selector '.sn-screen {
font: normal 100% "Courier New", monospace; background: #DDD; padding: 8pt }'. 
In my pages, I use '<pre class="sn-screen"> stuff </pre>'.  What actually gets
output to the browser is '<pre> stuff </pre>'--the class, and hence the
associated formatting, is stripped out.  

Other elements don't have this problem.  For example '<p class="sn-screen">' is
output as expected.  

As a workaround, I defined the default formatting for <pre> to be what I want
for screen output ... but then ALL <pre> formatted elements come up the same,
which really isn't what I want.
Comment 1 Brion Vibber 2005-12-15 19:34:36 UTC

*** This bug has been marked as a duplicate of 3935 ***

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