265661 - intermittent overlapping or misplaced text; reload fixes

Status: RESOLVED DUPLICATE of bug 217527

(Firefox :: General, defect)

Description

[Tony Tovar]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

With several web-site, e.g. http://www.theregister.co.uk ,
http://www.slashdot.org , etc, I will right-click on the various story links and
open them in New Windows or New Tabs.  About 25% of them will open with the
table or columns misplaced.  Reloading the page almost always fixes the problem,
so I don't think it's a 'bug' in the sites' HTML.

With The Register, the center column (main text) will be positioned too far to
the right, making the left-hand menu 2x or 3x wider than intended.

With Slashdot, the center column (main text) will be positioned too far to the
left, overlapping the menus.

Reproducible: Sometimes
Steps to Reproduce:

Comment 1

[Michael Thome]

I've been seeing this for a *long* time - just now with slashdot on 1.0RC1:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1

Comment 2

[Michael Thome]

Attachment: example

As you can see, really annoying.

Comment 3

[Tony Tovar]

Thanks for the screenshot, Michael!  Yep, that's basically what I'm seeing, too.

After I submitted this bug, I realized that I'd had something similar in the
past and it'd turned-out to be a bug in my AdSubtract software.  So I disabled
AdSubtract and I'm waiting to see if the problem goes away.  I think I got the
overlap once but then I'm not sure if I had AdSubtract disabled correctly.  Now
I'm sure it's "off" and I'm gonna give it a week or so.

You're not using AdSubtract (or other HTTP proxy), are you?

Comment 4

[Tony Tovar]

This appears to be a dupe of bug 217527 which has been trying to fix a subtle
table-layout issue since Aug '03.  They think they've finally (as of Sep. '04)
fixed it but it was too late to include it in Firefox 1.0.  Instead, it'll be in
Firefox 1.1 (and beta's thereof).

*** This bug has been marked as a duplicate of 217527 ***