Page MenuHomePhabricator

Text Overlap
Closed, ResolvedPublic

Description

Author: Thesevenoceans

Description:
The text does not wrap around the picture properly and overlaps onto it when a large picture is placed directly underneath a smaller one. Also icons are not positioned as they should be.

More Examples

http://en.wikipedia.org/w/index.php?title=Equinox&oldid=307052491
http://en.wikipedia.org/w/index.php?title=Twilight&oldid=309071030


Version: unspecified
Severity: major
URL: http://en.wikipedia.org/wiki/User:Acalamari

Details

Reference
bz20640

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:50 PM
bzimport set Reference to bz20640.

(In reply to comment #0)

The text does not wrap around the picture properly and overlaps onto it when a
large picture is placed directly underneath a smaller one. Also icons are not
positioned as they should be.

More Examples

http://en.wikipedia.org/w/index.php?title=Equinox&oldid=307052491
http://en.wikipedia.org/w/index.php?title=Twilight&oldid=309071030

Confirmed that this happens for the last image of each of these two pages.

Assigning to Nimish as Trevor's currently out on paternity leave.

ngautam wrote:

Seen on Safari and FF-windows

If I remember correctly, we have seen this with infoboxes and article message boxes as well. In the case of floating content, what matters in order to "clear" to the next line, is the top vertical height of the content. Whichever element is "highest" gets the priority. The line is 1 em high. But the image has a top border of 0.5em (and it's content is thus 0.5 em lower than the surrounding text). This gives the surrounding text vertical order precedence in some cases over the image. The indent is only readjusted on the next line of the surrounding text as a consequence.

All our images have this problem, but because of the relative distance between the last and the previous image, and one image wider than the one before it, such as in these examples, it makes it easier to trigger the problem.

  • This bug has been marked as a duplicate of bug 5118 ***