10

This question has a weird case of the mono, while the preview doesn't.

Also, that question is missing some content at the end:

13
  • We got a bleeder!
    – random
    Commented Apr 12, 2010 at 14:03
  • 3
    doesn't bleed for me (Firefox 3.6).
    – kennytm
    Commented Apr 12, 2010 at 14:11
  • Why am I not seeing it? Is it browser-specific? (FF 3.0.18)
    – Aarobot
    Commented Apr 12, 2010 at 14:11
  • 2
    CODE BLUE! CODE BLUE!
    – Jon Seigel
    Commented Apr 12, 2010 at 14:14
  • @json: Have you been kissing your monitor? Commented Apr 12, 2010 at 14:19
  • Try editing one of a posts in Opera. Hilarious results.
    – random
    Commented Apr 12, 2010 at 14:21
  • So this is [status-completed]? Kind of?
    – perbert
    Commented Apr 12, 2010 at 14:25
  • You'll have to give up a tag if you want status-completed.
    – random
    Commented Apr 12, 2010 at 14:26
  • @random: lose the browser specific tags.
    – perbert
    Commented Apr 12, 2010 at 15:02
  • 4
    @json @random - I'm pretty sure people will search more by the browser tags than the tag bleeding-style
    – Pollyanna
    Commented Apr 12, 2010 at 15:03
  • @Pol, you either leave the [bleeding-style] tag or I'll add a [mononucleosis] tag.
    – perbert
    Commented Apr 12, 2010 at 15:42
  • @Popular, check the screenshots. The question was truncated and there was a <code> tag unclosed, giving a monospace font to things that normally shouldn't have one. Now it was fixed by editing the question.
    – perbert
    Commented Apr 12, 2010 at 19:32

1 Answer 1

8

The HTML was incomplete and needed to be refreshed from the markdown. I did a trivial edit and this issue should be fixed for this post.

The SO team has elected not to go through the entire site fixing these problem posts so they have to be done by hand when found.

You must log in to answer this question.

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