Last modified: 2010-05-15 15:59: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 11671 - Conditional + span failure
Conditional + span failure
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
PC Linux
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-10-15 16:48 UTC by Aaron Sherman
Modified: 2010-05-15 15:59 UTC (History)
1 user (show)

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


Description Aaron Sherman 2007-10-15 16:48:34 UTC
I have a template that invokes another template like so:


I tried to convert this template to include a font coloration as a third parameter:

  {{wowlink|{{#if:{{{3|}}}|<span style="color:

And it rendered like so (the start of the rendered template only):


Notice the }"> that's being rendered as text. So, it seems that the parser is becoming confused over the nesting of parameter substitution and quoting. My assumption is that this is a bug, and I haven't found anything that contradicts that assumption, but if anyone has information to the contrary, I'd be happy to hear it.

The template now (correct, but without color support):

The template version with the bug:
Comment 1 Aaron Sherman 2007-10-15 16:52:14 UTC
Oops, I had an extra set of }} in that, but the bug still remains the same. See the corrected version that still demonstrates the bug at:
Comment 2 Aaron Schulz 2008-09-12 14:05:01 UTC
Works fine as of HEAD (1.14a) with the new Parser. OldParser still parses this brokenly. On the other hand, it's not really supported too much anymore.

I'd recommend upgrading.

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