Wikimedia Bugzilla is closed!

(may not be a dpl bug, but meh.)

That's kind of odd. I think we should get rid of the leading <br/> rather than adding one to the error message.

Check to see if you remove the newline between the <td> and the <dynamicpagelist> if that kills the br. (Could just be the double newline in a row causes parser to insert br. Should perhaps still do something about that, but less of an issue if there is such an easy work around)


(As an aside, those error messages are customizable, so you could add a br manually if you need to)

(In reply to comment #2)
> That's kind of odd. I think we should get rid of the leading <br/> rather than
> adding one to the error message.
> 
> Check to see if you remove the newline between the <td> and the
> <dynamicpagelist> if that kills the br. (Could just be the double newline in a
> row causes parser to insert br. Should perhaps still do something about that,
> but less of an issue if there is such an easy work around)
> 
> 
> (As an aside, those error messages are customizable, so you could add a br
> manually if you need to)


Yep, removing the newline kills the br. Still weird, but not the extension's behavior?

Yah, I knew the error message was customizable. Too lazy.

>but not the extension's
>behavior?

Sort of the extensions fault. What happens is: method=none triggers $startList = '';. Later on we have $output = $startList . "\n";. If there is a newline preceeding the dpl, that results in two new lines in a row. Parser sees two newlines in a row, and interprets it as a <br/>. Extension could be changed to not output that newline at begining and behaviour would go away (or it could be changed to disable that part of parsing on its output and the issue would go away, but that might have unintended consequences)