Last modified: 2010-09-29 21:53:09 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 13238 - <nowiki> inside a <pre> is not rendered on page.
<nowiki> inside a <pre> is not rendered on page.
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: need-parsertest, parser
Depends on:
  Show dependency treegraph
Reported: 2008-03-03 20:02 UTC by TRas
Modified: 2010-09-29 21:53 UTC (History)
3 users (show)

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


Description TRas 2008-03-03 20:02:06 UTC
When placing a <nowiki> inside a <pre> tag, the <nowiki> is lost on the rendering of the page.  Because it is inside a <pre> tag, the parser should leave the <nowiki> as text inside the <pre>.

Refer to the text on under Categories.
Comment 1 bdk 2008-03-04 21:09:26 UTC
This is expected behaviour imo. If you want to keep <nowiki> inside <pre> tags, you can use
This works well.
Comment 2 Antoine "hashar" Musso (WMF) 2010-09-29 20:50:38 UTC
Need a parser test. Any documentation about <pre> should mention it is not like <nowiki>.
Comment 3 Platonides 2010-09-29 21:53:09 UTC
Well, it's a bit confusing since a single <nowiki> would be rendered literal.

However, per another parserTest, the <nowiki> act inside pre for compatibility with pre-1.7

Added parser tests in r73988.

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