66088 - Mangled button when contents built during onload

Status: RESOLVED DUPLICATE of bug 50217

(Core :: XUL, defect)

Description

[Becki Sanford]

From Bugzilla Helper:
User-Agent: Mozilla/4.72 [en] (X11; U; Linux 2.4.0-test10 i686)
BuildID:    Mozilla 0.7

Changing window content during onload event may cause incorrect button element
positioning/display.

Reproducible: Always
Steps to Reproduce:
1.Launch mozilla with the attached XUL
2.
3.

Actual Results:  The parts of the button element are displayed adjacent each
other.

Expected Results:  The parts of the button element should be displayed on top of
each other.

I apologize in advance if this is a duplicate bug.  Wasn't exactly sure what to
search on. 

The attached XUL may seem a little strange but it's a stripped down version of a
dynamically built dialog window.  The full-blown version allows the user to
specify the icon image, 1 or 2 html elements, how many buttons to display and
what their labels will be.  (A nice, little generic window.)

The same code didn't work even in Mozilla M18 (guess I didn't notice until
today).

Comment 1

[Becki Sanford]

Attachment: Sample XUL which demonstrates this bug

Comment 2

[Becki Sanford]

I should point out if you uncomment the window.resizeBy() line, the window and
button will be displayed properly.  Yes, I realize that's a kludge but I'm good
at those :-)

Comment 3

[John Morrison]

Nice test case. However, this works fine for me .. I don't see anything 
odd about what's displayed, in either modern or classic skins. Could you
attach a screenshot?

There are some bugs around about display problems related to box layout 
combined with HTML layout regions, and they seem to occur more on linux 
than win32 or mac.

Comment 4

[Becki Sanford]

Attachment: Screen snapshot of button problem

Comment 5

[John Morrison]

Ah right (I was running in the browser, without the narrow width). This is 
the same deal as bug 50217 (which is being noticed in various similar 
situations).

-> evaughan

Comment 6

[Peter Trudelle]

Marking as duplicate fo 50217, but will check when that is fixed (scheduled 0.9)

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