117835 - overflow DIV property causes table mis-alignment

Status: RESOLVED WORKSFORME

(Core :: Layout, defect)

Description

[uberl0rd]

Really wierd one this - only started happening in 0.9.7. Also happens in latest
nightly (2002-01-06).

Basically, whenever you use overflow (auto and scroll values tested) in a DIV
element then any tables inside this element cannot be horizontally centered
using <table align="center">. Instead they almost (sometimes it works) appear at
the leftmost side of the DIV. Refreshing the page as no effect, but resizing the
window fixes it. After resizing, clicking on a form submit button inside this
table causes the table to jump back to the left again.

Comment 1

[Chris Petersen]

Reporter, please attachment a sample test case of the problem described.

Comment 2

[uberl0rd]

Attachment: overflow: auto causes mis-alignment

This is basically the default test12.html that ships with Mozilla that I've
hacked to duplicate the bug. To repliate, simply open the page (you may need to
refresh after loading). The main and footer sections will appear in the top
left most corner of the DIV - this is the problem. Resize the Mozilla window
and they will magically jump to their correct positions

it appears to also affect any block element (ie DIV) positioned with CSS

HTH

Comment 3

[Chris Petersen]

Changing component to style system

Comment 4

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Changing component back to layout.  I think this is a duplicate, though.

Comment 5

[Christopher Hoess (gone)]

Oddly enough, in today's CVS, I only see the footer out of position.

Comment 6

[Chad Gatesman]

Is there any way we can move this down to an earlier milestone?  This is a
pretty nasty layout bug.

Comment 7

[uberl0rd]

I certainly hope so - my intranet that our company sells is a bit foobar'ed
because of this. It worked fine in 0.9.6, but I couldn't use that as anchor
points didn't work on pages ending with .php. Iratating, as 0.9.7 fixed the
anchors, but broke the layout.

Comment 8

[uberl0rd]

Looks like this has been fixed in the RC1 build :)
I'll verify on a few more sites if I get time tomorrow

Comment 9

[Bernd]

wfm winnt 2002112512 + reporters comment