261376 - the whole content container (which is in a table) is shifted ~600px to the right

Status: RESOLVED WORKSFORME

(Core :: Layout: Block and Inline, defect)

Description

[Peter Gruendler]

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

In MSIE 6.0 the table has a left margin of ~15px.
There are numerous code quirks in the lines startingfrom line 68, but I still
wanted to let you know, as in quirks mode it seems to be possible to display it
as seemingly intended by the authors.

Reproducible: Always
Steps to Reproduce:
1. display the URI

Comment 1

[José Jeria]

WFM. Can you attach a screenshot of what is wrong witht this page? Looks the
same as in IE 6

Comment 2

[Peter Gruendler]

Attachment: collage of scrolled window made in photoshop to display whole viewport

Comment 3

[Peter van der Woude [:Peter6]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040924
Firefox/0.10

WFM

Comment 4

[José Jeria]

Can you retest in safe mode? Same results?

Comment 5

[Peter Gruendler]

(In reply to comment #4)
> Can you retest in safe mode? Same results?

yes.
It ssems to be a timing problem:
repeatedly selecting the same menu item leads to the page randomly being
displayed correctly or destroyed.
This is on a Dell Latitude X300 Notebook (1,2MHz Pentium M; with 1,13GB RAM),
which is not a very fast machine vor Windows XP SP2.

I remember a similar behaviour was reported in the .6 or .7 stages for
http://derstandard.at and turned out to be some kind of timing problem; but I
could'nt locate it in bugzilla.

Comment 6

[José Jeria]

You are running with the default options? Or have you changed anything via
prefs.js or about:config

Comment 7

[Peter Gruendler]

(In reply to comment #6)
> You are running with the default options?

As far as I can remember, yes. I also deinstalled older versions before upgrading.

> Or have you changed anything via
> prefs.js or about:config

besides the additions made by the adblock and web developer plugins, no.
adblock was disabled for reproducing the behaviour.
you can find the files here:
http://gruendler.org/bugzilla/

I'll also check on another faster machine within the next hours. If the
behaviour is different, I'll report it here.

Comment 8

[Peter Gruendler]

On testing on the second machine, which had still 0.9.3, I could track it down
to Adblock 0.5.2.039.

0.9.3 w/o adblock: page renders fine
0.10 w/o adblock: same.
0.10 w/adblock: the error occurs.
This is independent of the activation status of adblock.
Disabling adblock will not change the behaviour.

A note has been dropped on the adblock project forum.
Peter

Comment 9

[kstahl]

WFM with Firefox 1.0PR and Adblock 0.5 d2 nightly 39.

Comment 10

[Peter Gruendler]

(In reply to comment #9)
> WFM with Firefox 1.0PR and Adblock 0.5 d2 nightly 39.
> 

that's interesting - I can reproduce it (and repair it by deinstalling adblock)
on at least two (of two tested) machines.
I'll dig a little deeper tomorrow with more machines and have a look at the user
rights and the like.

Comment 11

[Anne (:annevk)]

Not a specific Firefox or Firefox Web Site problem.

Comment 12

[Martijn Wargers (dead)]

Clicking on the text in the content area (in the area of "Schlafen macht schön")
causes the bug for me, using:
Mozilla/5.0 (Windows; U; Windows NT 5.1; @AB_CD@; rv:1.8a4) Gecko/20040923
Firefox/0.9.1+
(This will not happen in 1.7 builds, because only in 1.8 builds overflow:auto
div's get a focus ring) 

Comment 13

[Martijn Wargers (dead)]

Attachment: Testcase

Comment 14

[Ronald Tilby]

Mozilla Windows Trunk Nightly Build TESTCASE Regression Window
Pass: 2004090105
Fail: 2004090206
URL Regression window to be determined.

Comment 15

[Martijn Wargers (dead)]

Attachment: Testcase2

The first testcase isn't showing the bug anymore, because overflow:auto <div>'s
don't get automatically a focus outline anymore.

Comment 16

[Peter Gruendler]

(In reply to comment #15)
> Created an attachment (id=170338) [edit]
> Testcase2
> 
> The first testcase isn't showing the bug anymore, because overflow:auto <div>'s
> don't get automatically a focus outline anymore.

Dou yo see the reportet behavior with the URI I originalle reported?
If not, can you let me know the build number you are referring to?
Build 20041108 (FF1.0 official release) still shows the behaviour reportet just
like in comment #5.

Comment 17

[Martijn Wargers (dead)]

Latest trunk (1.8a) build, which is currently 2005-01-04.
The url testcase is also still showing the bug for me.

Comment 18

[Asa Dotzler [:asa]]

dbaron, roc, bz, is this something we need to get for 1.8a6? If so, who can help?

Comment 19

[Bernd]

the patch in bug 276286 fixes Testcase2

Comment 20

[Boris Zbarsky [:bzbarsky]]

Fixed by patch in bug 276286

Comment 21

[Peter Gruendler]

The patch also resolves a problem with http://derstandard.at, where the bottom
frame was intermittently displayed in the vertical center of the draw pane while
resizing the window.

Comment 22

[Martijn Wargers (dead)]

Reopening, testcase2 is solved, but the url still shows the bug.

Comment 23

[Martijn Wargers (dead)]

Attachment: Testcase3

This testcase still shows the bug for me in 2004-01-10 Firefox trunk build.

Comment 24

[Boris Zbarsky [:bzbarsky]]

If that's the testcase, this is a duplicate....

Comment 25

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Bernd, this looks like one for you

Comment 26

[Caleb]

I can't seem to reproduce any of the testcases with Mozilla/5.0 (Windows; U;
Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050428 Firefox/1.0+

WFM.

Comment 27

[Martijn Wargers (dead)]

Yes, this is probably fixed by the fix for bug 240276.
The url works fine now. Although the testcases (testcase3) react a bit strange
now, it is probably not unexpected behavior.

Comment 28

[Peter Gruendler]

Ok, WFM too now.

Comment 29

[Boris Zbarsky [:bzbarsky]]

Actually, we could use a followup bug on testcase 3.  Martijn, want to file one?
 Please cc roc...

Comment 30

[Martijn Wargers (dead)]

(In reply to comment #29)
> Actually, we could use a followup bug on testcase 3.  Martijn, want to file one?
>  Please cc roc...
Actually, I now think the remaining issue in testcase 3 is bug 286368.