Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 155 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

In the question What makes a good tag-wiki entry? from meta.tex.sx, the input ... [tag:linguistics], ... (without a space before the comma) is rendered as follows (no free-hand circles, sorry):

The comma shouldn't start the 2nd line, obviously. Can this please be fixed?

EDIT: Here's another instance where the result looks much worse in my opinion, with just ")." on the last line. For me, the question Merge {conditional} and {ifthen} renders as

share|improve this question
1  
how in the world is this our bug? – Jeff Atwood Mar 31 '11 at 9:44
    
@Jeff: Honestly? I had no idea whatsoever what this bug is caused by (due to lack of knowledge). From your comment and retagging I gather it could be a bug in Firefox 3.6, but I didn't think of this when posting the question. – Hendrik Vogt Mar 31 '11 at 13:18
    
@Jeff: OK, I don't know much about CSS, but I investigated a bit. In .post-tag I see both display:inline-block; and white-space:nowrap;, and Firefox 3.6 doesn't seem to like this combination. (I can't tell if Firefox should like it). I gather the inline-block is needed for margin:2px 2px 6px 0; taking effect, but I think the latter could be avoided. Then one could fix the bug by just omitting display:inline-block;. As I say, I'm not a CSS expert, but if a major established browser like Firefox 3.6 shows this behaviour, it's worth fixing this, and yes, partly it is your bug. – Hendrik Vogt Mar 31 '11 at 15:08

I've given it +1 because it's a reasonable question to ask. However, I think it's probably quite tricky to fix; it's more of a quirk in the browser's rendering engine than something the site could do anything about.

It's also something of an edge case, dependant on the exact combination of browser/OS/font as much as it is on the text itself -- I'm not seeing it when I browse to the same URL.

share|improve this answer
    
Thanks for the feedback. Of course the actual point of the line break depends on a lot of stuff, but it would be interesting to know if the possibility of a line break before the comma depends on the browser/OS/font. – Hendrik Vogt Feb 24 '11 at 15:30

You must log in to answer this question.

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