Last modified: 2010-09-29 21:53:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T15238, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 13238 - <nowiki> inside a <pre> is not rendered on page.
<nowiki> inside a <pre> is not rendered on page.
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!
http://en.wikipedia.org/wiki/Category...
: need-parsertest, parser
Depends on:
Blocks:
  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: ---


Attachments

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 http://en.wikipedia.org/wiki/Category:Sorority_and_fraternity_user_templates 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
<pre><nowiki><nowiki></nowiki>Foo<nowiki></nowiki></nowiki></pre>
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.


Navigation
Links