36

When a comment on a suggested edit is long enough to be on two lines, part of the descender of the first line is being eaten by the line beneath.

Pixel overflow!

I'm on Chrome 27.0.1453.94 m and Windows 7 if it's relevant.

You can see what is happening when selecting the text:

selected

0

I'll repost my answer from a related question here (since my question with more details is probably soon to be closed) as suggestion for quick/possible fixes.

I've just ran into a Suggested Edit which present the same issue. The comment is barely readable, given that the 2nd (and subsequent) lines overlap half of the previous. This phenomenon also happens in the individual revision page.


The issue seems to be the CSS applied to the body element: line-height: 1;.

Disabling/removing this entry makes the comment expand properly (along with several other element sizing on the page). Here's a screenshot showing the correct-looking comment:

Screenshot showing the proper look


An alternative solution (so as to not mess with the rest of the design) is to add line-height: 1.4em; to the revision-comment CSS class.

  • That comment doesn’t look correct-looking. – Ry- Sep 3 '13 at 18:26
  • To which comment are you referring? – Jesse Sep 4 '13 at 2:40
  • 1
    The comment in your screenshot that you said was correct-looking. The “g”s are still cut off…? – Ry- Sep 4 '13 at 2:42
  • You're right; I hadn't noticed that detail. This was fixed about three months ago, though. – Jesse Sep 4 '13 at 2:45

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .