This is very painful to look at. We understand appearances are everything, but there's no need to exaggerate. Could you please bring them back down to regular size?

It also throws off the formatting layouts. The top of the diamond is cut off on every post, and it expands the comment box by about two or three pixels.

Browser: Chrome for Android (Nexus 7, Jellybean 4.1). Screenshot is in desktop mode, though the problem is present in normal view as well.

screenshot of diamond largess

  • I get the same thing on Linux… sometimes. I’m not sure when or why. (Not quite that big, though.)
    – Ry-
    May 20, 2013 at 0:34
  • I have the same problem on the regular Android browser on a Samsung Galaxy S3 with Android 4.1.2.
    – user215114
    Sep 12, 2013 at 17:18
  • Same problem with Galaxy Nexus with Android 4.3 Dec 23, 2013 at 13:08
  • 9
    They're just compensating. ;-) Feb 12, 2014 at 2:46
  • @LightnessRacesinOrbit Certainly not to be confused with an ego-indicator. ;) /* Just kidding… */
    – e-sushi
    Feb 18, 2014 at 20:21
  • 1
    Seems more like a CSS rendering bug than an intentional design choice. Suggest rephrasing your question to be more about the actual issue, rather than posing it as a design choice that was made by the design/dev on the site.
    – Chad Udell
    Mar 8, 2014 at 16:10
  • @Chad, I guess it's just a different font (as used by the browser to render that character). But surely that's indeed not a design choice either.
    – Arjan
    Mar 8, 2014 at 16:34
  • @Chad I never claimed it was a design choice, only that it's incorrect.
    – user206222
    Mar 8, 2014 at 20:12

1 Answer 1


I have heard corroboration of this problem for the mobile side but I haven't been able to reproduce this (or find someone who has) as of today, so I think it's likely that the recently-refreshed mobile site has probably obsoleted the problem. I don't have a good explanation for why it would have appeared on the desktop site, but still: I can't reproduce, so we'll call it completed.

  • Looks like it's fixed, as I can't repro the problem on the latest Chrome for Android (37) on the desktop site.
    – hichris123
    Sep 24, 2014 at 20:54

You must log in to answer this question.