Last modified: 2011-04-30 01:21:41 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T26844, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 24844 - Template using a template which is creating a (wikisyntax)-table is creating a leading linebreak
Template using a template which is creating a (wikisyntax)-table is creating ...
Status: NEW
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
1.15.x
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-18 09:07 UTC by Daniel A. R. Werner
Modified: 2011-04-30 01:21 UTC (History)
0 users

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


Attachments

Description Daniel A. R. Werner 2010-08-18 09:07:05 UTC
When you have a template "A" which is calling another template "B" which will return a wiki table created by wiki syntax, in the end you get a leading line break before the table when calling template "A".

Using template "B" instead wouldn't result in a leading linebreak.

This whole thing can break the nice look of the page because it is creating void <p></p> paragraphs when using template "A" to times in a row with a void line inbetween like:

{{A |...}}

{{A |...}}

And It's quiet confusing when using

{{A |...}}

{{A |...}}

{{B |...}}

{{B |...}}

because there is no logical explanation why the space between A, B and B looks pretty nice, the space between A and A on the other hand is much bigger because of <p></p>

Another thing is, that the whole thing would work fine with HTML table syntax. Looks like the bug lays somewhere within the wiki table syntax.

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


Navigation
Links