Closed
Bug 523058
Opened 16 years ago
Closed 16 years ago
The maximize button acts weird in MacOS X
Categories
(Thunderbird :: OS Integration, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: postmaster, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)
Build Identifier: version 2.0.0.23 (20090812)
The maximize button does not maximize Thunderbird in MacOS X.
Reproducible: Always
Steps to Reproduce:
1. Open Thunderbird
2. Resize it to a random size (middle of the screen for example)
3. Click the green maximize button (right top of the window)
Actual Results:
Thunderbird does not cover the whole screen
Expected Results:
Thunderbird should cover the whole screen (except for the dock and other static UI elements, of course)
Generally, the window ends up covering the screen in height, but not in width
The same bug also applies to the "Message Composer" window in Thunderbird
The maximize button behaves correctly with Firefox, Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3
Comment 1•16 years ago
|
||
Well, no, it behaves incorrectly in Fx 3.5.x, since there is no "maximize" button in OS X, there's a "zoom" button, which is supposed to toggle between the optimum size for the content being displayed and the size from the last time that you resized the window to something more than 7px away from the optimum size. The only way it's ever supposed to act as a maximize button is if you manually dragged the window size and position to be maximized some time in the past.
However, since the behavior of that button is a core function, Tb will stop behaving like Fx 2.x did and start behaving exactly like Fx 3.5.x does, once Tb 3 ships using the same backend as Fx 3.5.x.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Comment 2•16 years ago
|
||
Verified. OS X behaves differently. It's Thunderbird that does it correctly, Firefox is wrong, and should be fixed (see bug 232919).
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•