Revision mark-down source diff bug

Is this a bug of Stack Overflow, or this is a browser bug? The text is not wrapped properly.

I'm using Firefox 14.0.1 on Windows 7. The page in the screenshot is the revision page of this question.

I fiddled around with the inspector in Firefox. After I changed the property white-space from pre to pre-wrap for #revisions .markdown-diff .full-diff td.content, then the problem disappeared.

-
Wraps fine here (SeaMonkey). Browser bug. – Daniel Fischer Aug 2 '12 at 14:11
No such issue in Chrome either. – Bart Aug 2 '12 at 14:13
Wraps fine on FF14.0.1 running on Win 7. – H.Muster Aug 2 '12 at 14:21
@H.Muster: Not sure, I even open it on a clean profile. It has the same overflowing text problem. – nhahtdh Aug 2 '12 at 14:23
@nhahtdh: Funny: I can reproduce this bug when use Private Browsing (i.e. then I am logged out + no cookies). But while logged in, everything looks fine. – H.Muster Aug 2 '12 at 14:27
I see it on 14.0.1 on Mac as well. – Martijn Pieters Aug 2 '12 at 14:29
FF 14.0.1 Ubuntu, same bug. – msh210 Aug 2 '12 at 16:47
Just saw it here: stackoverflow.com/posts/11470451/revisions – BoltClock's a Unicorn Aug 2 '12 at 17:31

It appears we've hit an area here where CSS browser compatibility can still use some work. I checked five browsers, and got three different results: Safari and IE agree, Chrome and Opera agree, and Firefox stands all alone, also being the only one where it looks really totally broken.

When using pre-wrap as Martijn Pieters suggests (and it's really the better solution), they all agree. Fixed in the next build. Thanks!

-
I may just be spoiled by how efficient you usually are, but has the build in question gone out? I'm still seeing the bug at this suggested edit. – Pops Aug 3 '12 at 16:24
No, it's not yet. I'll build out in a few minutes. – balpha Aug 3 '12 at 17:11
Should be good now. – balpha Aug 3 '12 at 17:18
Yep, looks fixed. – Pops Aug 3 '12 at 17:22

I certainly see this on Mac OS X 10.7.4, Firefox 14.0.1 as well.

The use of the white-space CSS property is a recent change, and I think it wasn't tested with enough diffs. Using pre-wrap instead of pre is, to my eyes, the correct fix.

-