Rendering bug in Firefox

[anonymous]

In the diff view, it sometimes happens that the content column gets very narrow, in Firefox (Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1).

I noticed this bug first on my trac, but now it also shows up on the edgewall trac for changeset [1010], so I take this opportunity to create a ticket for it.

Most certainly it's a bug in Firefox, but maybe some CSS wizard will find a workaround for this...

Pictures showing the bug attached:

• Abnormal rendering in Firefox:

http://projects.edgewall.com/trac/attachment/ticket/875/ff_1010.png?format=raw

attachment:ff_1010.png

• Normal rendering in IE:

http://projects.edgewall.com/trac/attachment/ticket/875/ie_1010.png?format=raw

attachment:ie_1010.png

[cboos@…]

Firefox rendering of [1010]

[cboos@…]

IE rendering of [1010]

[matthew@…]

For what it's worth, it renders fine for me on 1.0RC1 and 1.0RC2.

[anonymous]

Works for me on Firefox 1.0PR and Linux

[cmlenz]

Works for me on Firefox 1.0RC1 on Windows and Mac OS X.

Is this problem consistently reproducible over the same changesets, or does it go away on reload etc. What is the exact version of Firefox you're using, and on what platform?

[cmlenz]

Forget the question about the version/platform. I should have read the description properly :-P

[cboos@…]

I upgrated to Firefox 1.0, and it still doesn't work for me... Strange.

[cboos@…]

The bug shows up also in [1073].

[cboos@…]

Also, when I save the file source locally, and change it so that it uses the CSS from my local trac installation (rev [1061]), the page is rendered correctly. So it's quite difficult to debug :)

[cboos@…]

More fun with this issue:

• While browsing [1327] (the latest at this time), I noticed the display problem once again, so I decided to try the Web Developer extension Edit CSS... feature to see if I could improve things... and the simple fact of launching the editor did solve the layout problem!
• I tried to quit/restart Firefox: it was still OK
• I can even see [1010] and [1073] without any problem now

So, whatever was that bug, I think that now it works for me :)