-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jim Wilson wrote:
There's been some recent discussion in the mediawiki IRC channel about the Parser's handling of whitespace in tag extension output. Specifically, if the output of a tag contains leading whitespace or consecutive newlines, they are replaced with <pre> blocks and </p><p> combos respectively.
The general problem IIRC is that until the extension block's contents are replaced it's not necessarily clear whether it should be treated as a block element or an inline element.
Eg, you may need to wrap a <math> in <p>s but you shouldn't so wrap something that outputs itself as a <p> or a <pre> or whatever, or you end up with odd spacing and inconsistent markup.
I'm planning to fix this, and I was curious which version(s) would receive the fix when finished. Does this qualify as something which would be backported, or only in the latest release? Thanks in advance.
Backporting questions can usually be answered pretty easily:
a) Is it a security fix? no
b) Is it vital for the software to run? no
So, probably no. :)
In particular note that a change to parser behavior is the kind of thing we really *don't* want to introduce in a preexisting stable branch.
As an example of 'vital' fixes; a bug that causes MediaWiki to fail on a certain version of MySQL or a certain major web server might have a decent chance of being backported to the latest release branch if it's not a large change.
- -- brion vibber (brion @ pobox.com / brion @ wikimedia.org)