Last modified: 2011-03-13 18:05:27 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 13936 - parsing treats {{t|a}} differently from {{t|1=a}} with \n in output.
parsing treats {{t|a}} differently from {{t|1=a}} with \n in output.
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: parser
Depends on:
Blocks: 2376
  Show dependency treegraph
Reported: 2008-05-03 12:30 UTC by darklama
Modified: 2011-03-13 18:05 UTC (History)
2 users (show)

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


Description darklama 2008-05-03 12:30:22 UTC
For some reason when someone uses multiple lines for a template like:

| a

it includes a new line character in the output which leads to unexpected behavior. If however you use:

| 1=a

a new line character is not included in the output which is the expected behavior.

This problem exists in both the new and old parser from a what a quick Special:ParserDiffTest test shows.

"| a" should be treated the same as "| 1=a" by not including a new line character.
Comment 1 Tim Starling 2008-05-04 23:15:09 UTC
This is ancient accidental behaviour, reproduced at great expense in the new preprocessor for the sake of backwards compatibility. We had many complaints of broken articles in the brief period when the new preprocessor did not do this. So this is how it will stay.

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