Wedge

You forgot the usual OS/browser version, etc...

No such problem for me in Aurora Win 7.
Also works fine in regular Firefox in Ubuntu.

Ohhh...right... O:-)
Gomen. :youretheboss:

FF 25 OpenSuse... TBH I don't even know what's the current FF version, I may be several behind... :-S

Hmm, I thought Firefox had the same problem as Chrome, but it turns out it's worse in Firefox, as it screws up the flexbox even when there's a vertical scrollbar on the code block.
I've modified the script accordingly. Still doesn't make sense to me -- and I can't believe that Chrome and Firefox (but not IE :wow:) would fail at such a 'simple' layout as <flexbox><tag with white-space: pre></flexbox>... It's really, really just as simple as that. They suck at flexbox.

Chrome seems to work fine here (I used it to have the confirmation it was not a "major" problem), 31.something... OMG 31? O_O
That's a quite crazy numbering. LOL

It only works in Chrome because as there's a *vertical* scrollbar. If there's an *horizontal* scrollbar bar but NO vertical scrollbar, it starts behaving exactly the same as Firefox here, unless you do that: $('.post code').css('flex', 'none'); (This hack is signed yours truly. Of course, don't execute it if there's a vertical scrollbar or no horizontal scrollbar on that element. As a result, the code in Wedge is more complicated than that.)

I still don't know why both browsers fail at that, really. Flexbox is supposed to be the next big thing.
As a reminder, iOS 7 also supports flexbox, and also fails with it, this time with suggested flex widths.

It happen to me too yesterday when i was checking the topic about the unused globals, part of the "code box" was on top of your signature, but today its working fine, win 7 ff 25.0.1.

Is that feature the one that breaks again the layout? :P

Same details as above. ;)

Ah, an unrelated bug... Due to the border-box hack, applied recently as suggested over at... Elk ;)
It's working fine most of the time, but will need readjusting here and there, of course.
For instance, remotely the select boxes have faulty paddings right now, but they're fixed locally.

No you are not.

And I dedicate my latest commit to Xarcell... Who's the one actually responsible (--> here.)

I'd love to keep that in, but this morning I realized I had spent way too much time fixing related bugs, and it just upset me to think about it. I don't have time to waste on experiments these days. Only visible improvements, not 'theoretical' ones.