Last modified: 2010-05-15 15:56:51 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 6333 - <nowiki> tag doesn't work after upgrading from 1.6.3 to 1.6.7
<nowiki> tag doesn't work after upgrading from 1.6.3 to 1.6.7
Status: RESOLVED DUPLICATE of bug 1581
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.6.x
All Linux
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-06-16 21:00 UTC by Adam Sealey
Modified: 2010-05-15 15:56 UTC (History)
1 user (show)

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


Attachments

Description Adam Sealey 2006-06-16 21:00:10 UTC
I use the <nowiki> tag in conjunction with <pre> and <code> to insert multi-line
code snippets within an ordered list.  After upgrading to 1.6.7, the new parsing
of nowiki seems to not parse correctly.

Example:
# One <code><pre><nowiki>
multi
line
code
snippet
</nowiki></pre></code>
# Two

Results in the following HTML output

<ol><li> One <code><pre>
</li></ol>
<p>multi
line
code
snippet
</p>
</pre></code>
<ol><li> Two
</li></ol>

The <nowiki> tag appears to have had no effect (wiki still interpreted the CR as
the need to close the <li>.

Bug is also found at
http://meta.wikimedia.org/wiki/Help:Editing#Just_show_what_I_typed in the 4th
row, where the numbered list is supposed to continue, but doesn't.
Comment 1 Brion Vibber 2006-06-17 00:19:58 UTC

*** This bug has been marked as a duplicate of 1581 ***
Comment 2 Adam Sealey 2006-06-20 21:01:44 UTC
I agree, this seems to be a recurrence of that issue, but my point is that it
resurface between 1.6.3 and 1.6.7...all those suggestions are dealing with the
1.5.x code.

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


Navigation
Links