Last modified: 2007-10-27 21:19:52 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 11703 - Contents disappear if two <nowiki> tags inside a table
Contents disappear if two <nowiki> tags inside a table
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-10-18 21:03 UTC by suruena
Modified: 2007-10-27 21:19 UTC (History)
0 users

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


Description suruena 2007-10-18 21:03:32 UTC
If we use two pairs of <nowiki> tags inside a table cell to avoid two different internal links (wikis)--the first is a piped wiki, but not the second one--, the text of that cell is not shown until the pipe (see the link). However, if you edit the page the contents are still there (no data lost), they are simply not shown.

If the second wiki is piped, the text until that second pipe disappears, but the condition is the _two pairs_ of nowiki tags _inside a table_
Comment 1 Brion Vibber 2007-10-27 21:19:52 UTC
The | character is part of table syntax. When used inside a link, the link takes priority; when you de-link the link, then the | gets used as for tables.

In this instance, the "|blah | foo" construct means that "blah" is taken as HTML attributes for the table cell, and "foo" is the cell content.

You want to <nowiki> the whole link, probably.

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