Last modified: 2006-07-09 16:05:02 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 6607 - Need a line break between stub markers and body of article
Need a line break between stub markers and body of article
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
PC Windows XP
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-07-09 15:43 UTC by Richard Norton
Modified: 2006-07-09 16:05 UTC (History)
0 users

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


Description Richard Norton 2006-07-09 15:43:31 UTC
== Stub Templates in Wikipedia ==

I want to suggest that stub templates get a line break between them and the text
of the article. Where is the proper forum for me to suggest it? It would be best
if it was built into the software rather then dependent on the user to add the
break. Here are two examples of how they look with and without:
[ no line break]
[ added line break]
In the first example the graphic from the stub runs up directly against the text
preceding it and in the second example there is an added line break. One break
is needed between the first stub and the text, the stub markers dont need a line
break between them, just one above. Please write back if this isn't clear.
Comment 1 Rob Church 2006-07-09 16:05:02 UTC and the
associated discussion page might be the best venue for this.

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