Last modified: 2005-01-11 19:20:45 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 1276 - Feature Request: CSS and wiki markup for red warning text.
Feature Request: CSS and wiki markup for red warning text.
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-01-07 03:27 UTC by Toby Bartels
Modified: 2005-01-11 19:20 UTC (History)
0 users

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


Description Toby Bartels 2005-01-07 03:27:35 UTC
First, the red warning text that appears in some places (like the edit preview)
should always be properly done with CSS. (Aside from simple correctness, see
feature request [[989]] for a reason.) I'll suggest <class = "warning">.

But this only works in system text. Red warning text is also used in wiki-edited
text (see the top of [[w:en:Donations for victims of the 2004 Indian Ocean
earthquake]] for an example). So we should have a wiki markup for it. I'll
suggest "<warn>...</warn>", and if anybody objects to that on the grounds that
wiki tags shouldn't look like HTML tags (as <nowiki> does), then I'll let them
suggest an alternative ^_^.
Comment 1 Brion Vibber 2005-01-07 03:54:41 UTC
<p class="error">bla bla</p>
Comment 2 Toby Bartels 2005-01-11 19:20:45 UTC
Thanks, Brion! It works great.

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