271922 - loss of resize handle when forcibly moved from one display to another

Status: RESOLVED EXPIRED

(Firefox :: Shell Integration, defect)

Description

[Michael Stillwell]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I have a Powerbook, which supports an external display.  If I run Firefox on the
external display, and have the window sized greater than 1024x768 (the
powerbook's native resolution) then if I send the powerbook to sleep, unplug the
external display, then wake the powerbook up again, the firefox window is
resize, but omly When the powerbook is plugged into the external display, but
only so much as to make the resize handle almost (but not quite) grabbable. 
Most other applications, including Safari, resize fine.

Reproducible: Always
Steps to Reproduce:
1. Plug in external display.
2. Start Firefox, and move it to the external display if necessary.
3. Enlarge the window so that it is larger (vertically) than the powerbook's
native display.
4. Put the computer to sleep.
5. Unplug the external monitor.
6. Wake the computer up.

Actual Results:  
The window is "migrated" to the powerbook's internal display, and the window
resized, but the resize window "handle" is not quite visible.  There appears to
be no way of resizing the window.

Expected Results:  
The resize window hotspot should be visible/accessible.  (The window is pushed
as far up as it will go.)

Comment 1

[Sameer]

Can confirm this bug on a powerbook OSX 10.3.6 using 
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041123

Comment 2

[Michael Stillwell]

This may not actually be related to the sleep/wake process; I get the same thing
when the displays change across reboots.  bug 218214 may be related; in fact
this may be a dupe of bug 218214.

Comment 3

[Gervase Markham [:gerv]]

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/

Comment 4

[Gervase Markham [:gerv]]

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.