Please look at the image.

The right column's text jumbles with some comment text when the comment contains a large amount of white-space inside an inline code block. I guess that's not the design may be the comments should be a little bit more restricted from expanding? What do you think?

enter image description here

Now even kinda worse:

enter image description here

  • This is the lINK:: stackoverflow.com/questions/22732371/… Mar 29, 2014 at 15:31
  • Looks like a Firefox-only side-affect again related to this change. I've just deleted the comments.
    – animuson StaffMod
    Mar 29, 2014 at 15:44
  • @animuson: And that's a CSS change affecting newlines in comments adding extra breaks. If we see this overflow behaviour in current FF than there is a different bug, one that doesn't properly wrap the comments (fewer newlines). Mar 29, 2014 at 15:46
  • @Martijn Yeah, it looks like there's just a crap-ton of white-space after each line in that particular comment. They should probably reconsider that change...
    – animuson StaffMod
    Mar 29, 2014 at 15:50
  • @WhoEverDeletedTheComments: So, will you be deleting all Cooments with CODES in the PAST and FUTURE???... Or instead of Deleting, why NOT UnBug the Bug? Mar 29, 2014 at 15:50
  • 1
    @Universal We generally delete comments with that much code in them anyways. They're noisy and ugly and don't belong in the comments.
    – animuson StaffMod
    Mar 29, 2014 at 15:52
  • @animuson Sure sounds fare.... just wondering how will the 100BILLION Registered Members know that their comments are prone to deletion. As a developper, I'd go for a Fix for the Bug and a Making of the ugly CODES look Great.... and Please let me have some UpVotes on this for myReps.... thx Mar 29, 2014 at 15:55
  • 3
    @Universal Yes, it should be fixed, but that has nothing to do with whether the comments should be deleted or not.
    – animuson StaffMod
    Mar 29, 2014 at 15:57
  • 1
    @UniversalGrasp we have to assume some members visit and read the faq
    – rene
    Mar 29, 2014 at 16:01
  • @animuson Ok, I agree... thx Mar 29, 2014 at 16:16
  • @glorfindel I can no longer reproduce this issue in firefox. So I think it would be best to let this post die, maybe even close it as no longer reproducable if others can't repro either. And let the other post live on as the chrome bug.
    – Luuklag
    Feb 22, 2021 at 14:16
  • @Luuklag hmm ... that makes sense. I can't repro it either. I'll rollback and retract the close vote.
    – Glorfindel Mod
    Feb 22, 2021 at 14:39
  • 1
    It was reproduced at the time it was reported as the tag indicates. it should not be closed but rather changed to status-completed.
    – TylerH
    Feb 22, 2021 at 15:02


Browse other questions tagged .