Closed Bug 269629 Opened 20 years ago Closed 19 years ago

mozilla does not start up maximized

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: hugovanwoerkomqt, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041112
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041112

Starting Mozilla, comes up small.
Maximize it. Quit Mozilla.
Start again: still comes up small.
Using: mozilla -width 1265 -height 983, like the -help says, has no effect.
Happens with all users, including new users with no .mozilla dir.
EXCEPT one user always starts maximized.

Reproducible: Always
Steps to Reproduce:
1.start mozilla. Maximize.
2.quit mozilla
3.start mozilla again: is not maximized.

Actual Results:  
Does not start maximized. But OK with one user on the system.

Expected Results:  
Always come up maximized.

This is like 257271, which says it is a dup, but does not say of what.
This used to never happen, until...
I switched XFree86 drivers, from Nvidia closed source to nv.
That needed modelines, which Nvidia does not.
I switched back again to Nvidia, but ever since then Mozilla does not remember
it was maximized.
You people are to be recommended for finding your way around in a snakepit. ;-) 
Unfortunately it is annoying: having to always click the maximize button, since
I always use Mozilla maximized...
Product: Browser → Seamonkey
Today (Dec. 1 2004) I noticed suddenly that Mozilla *was* starting up fullscreen.
And I must apologize that I did not notice when that started: in the past week
or something. I just did not notice that I did not have to hit the maximize
button anymore. This is on Linux Debian Sarge: I have not applied updates since
I filed the bug.
Today I downloaded both mozilla-i686-pc-linux-gnu-gtk2+xft-1.8a5.tar.gz  and 
mozilla-source-1.8a5.tar.bz2.

Installed both.

Upon starting noticed that https://bugzilla.mozilla.org/show_bug.cgi?id=214007
is there again: the chevron is gone from the personal toolbar.

So I looked at the comments and that mentioned that by "resizing" it will appear.

Sure enough.

AND this bug is back then: after resizing once and pressing the maximize button
on the window, Mozilla does NOT start up maximized anymore.

This time I will see if I can keep track of when it DOES start up maximized again.
This morning Mozilla started up fullscreen.
I have no idea what brought the change from yesterday when it did not.
Summary: mozilla does not remember fullscreen startup → mozilla does not start up maximized
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.