8468 - apprunner startup redraws at old size

Status: VERIFIED FIXED

(Core :: XUL, defect, P3)

Description

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

I've been seeing this for quite a while - for example on build of
1999-06-17-08-M7 (from mozilla.org), Linux.

Here's the sequence of events (* for me doing something):

* start apprunner
+ apprunner creates its window, blank
* before any chrome loads, I maximize the window
+ the chrome draws correctly to the maximized window size
+ THEN, right about when the startup page begins loading, the chrome redraws
back at the old size.
+ THEN, after the startup page is finished loading, the chrome redraws again at
the correct (maximized) size.

This makes startup very slow.  May be related to bug 7417.  Something seems to
be overwriting a new window size with an old one, or something like that.

Comment 1

[don]

David, is this our bug or a toolkit/widget issue?

Comment 2

[davidm]

toolkit as there is currently no XPApp code for doing autowindow sizing that I

amn aware of

Comment 3

[Peter Trudelle]

reassigning to evaughan for M8. Eric, will your size to content work fix this?

Comment 4

[leger]

Updating QA Contact.

Comment 5

[leger]

phillip, is this all platforms...or Linux specific?

Comment 6

[phillip]

this appears to be a linux only problem. i suppose one could turn off
double buffering and recompile the max/win builds in case it happens really
quickly on mac/win and we just don't see it happen, but i imagine it
has to do with X events. (that's a wild guess).

Comment 7

[Eric Vaughan]

looks like X stuff.

Comment 8

[Chris McAfee]

M9.

Comment 9

[Stuart Parmenter]

the window is the last thing being shown now, so by the time the window has
appeared the content will have been reflowed.

Comment 10

[phillip]

verified on

     1999-07-07-08 RedHat Linux 5.2 kernel 2.2.9

Comment 11

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

I am still seeing this on 1999-07-08-18, although for a shorter time because
things are faster.  You have to maximize at the right time.  Maximize right
*after* you see chrome draw for the first time, and it will get big (correct)
and then small again (incorrect) and then big again (correct).  Reopening bug.

Comment 12

[Stuart Parmenter]

its fixed.  i checked in the code at 10:00am or so which is after todays builds
went out.  try it again with a build from after 11:30am on 1999-07-09 to verify
this.

Comment 13

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

Verified fixed, using 1999-07-10-08-M8.