Closed Bug 299617 Opened 19 years ago Closed 15 years ago

When full-screen (not kiosk) and moved from one monitor to another, it goes into a strange kiosk mode

Categories

(Firefox :: General, defect)

1.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: moreno, Unassigned)

Details

(Whiteboard: closeme 2009-08-01)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

If resized to full screen (double-clicking on the title bar or whatever), then
moved to another monitor via other softwares, it behaves strangely, as displayed
here: http://www.blueworld.it/firefox.png

Reproducible: Always

Steps to Reproduce:
1. resize to full screen (i.e. by double clicking title bar)
2. move the window to another monitor via third party software (i.e. Matrox or ATI)
3. see what happens

Actual Results:  
If resized to full screen (double-clicking on the title bar or whatever), then
moved to another monitor via other softwares, it behaves strangely, as displayed
here: http://www.blueworld.it/firefox.png

Expected Results:  
Just move from one monitor to the other, without losing the titlebar.
All my colleagues (and me of course) in the company have this ugly bug.
My version:
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051114 Firefox/1.5

I can't remember having this behaviour with Firefox 1.0.7.
do you still see this problem? please update the bug with comment and/or close as appropriate.

(bug has no comment since 2007-01-01)
Whiteboard: closeme 2009-08-01
No reply, INCO. Please reopen if you are seeing this in Firefox 3.5.2 or later in Firefox safe mode and a new profile with the latest plugins.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Profiles
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Version: unspecified → 1.0 Branch
You need to log in before you can comment on or make changes to this bug.