Last modified: 2011-07-05 20:12:22 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 14242 - Insufficient line space between bullet point and TOC
Insufficient line space between bullet point and TOC
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.13.x
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikipedia.org/w/index.php?t...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-05-23 20:50 UTC by jeffb
Modified: 2011-07-05 20:12 UTC (History)
2 users (show)

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


Attachments

Description jeffb 2008-05-23 20:50:28 UTC
Compare these two cases:

1. Intro section ends with plain text and is followed by a TOC.
   Example: http://en.wikipedia.org/w/index.php?title=Electric_charge&oldid=214401911

2. Intro section ends with a bullet point and is followed by a TOC.
   Example: http://en.wikipedia.org/w/index.php?title=Electroscope&oldid=211103446

The line spacing after the bullet point is less than that after the plain text.  This makes case 2 look ugly.

Tested on: Firefox 3 beta 5, Ubuntu 8.04.
Comment 1 Siebrand Mazeland 2008-08-17 18:03:54 UTC
Please submit a patch for the css. Css is not my kind of thing.
Comment 2 Jarry1250 2011-07-05 20:12:22 UTC
Spacing now seems adequate on all the browsers I had to hand (Firefox 5 / Chrome 12 / IE 6, 7, 8 and 9).

Seems that the issue has been fixed (can't reproduce).

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


Navigation
Links