Closed Bug 78155 Opened 24 years ago Closed 15 years ago

maximized pop-up windows (via JavaScript, etc.) will not display on my second monitor

Categories

(SeaMonkey :: UI Design, defect)

Product:
SeaMonkey
Component:
UI Design
Platform:
x86
Windows 98
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED EXPIRED

People

(Reporter: otupman, Unassigned)

References

(
URL
)

Details

(Keywords: helpwanted, qawanted, relnote)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.8.1+) Gecko/20010428 BuildID: 2001042820 Running a dual-monitor system. View a website that brings up a pop-up window. The pop-up window will not display on the second monitor. Can drag it there, but no window appears - gets clipped at the edge of the screeen. Reproducible: Always Steps to Reproduce: 1. View website with pop-up windows. 2. Attempt to drag the pop-up across 3. Actual Results: The window still 'exists', but does is not displayed on the second monitor. Expected Results: Display the window on the second monitor.
0.9 has come out, could oyu try and see if this still happens?
Reporter: Can you try it with Mozilla 0.9.1 ? We will mark this bug worksforme if we don't get an answer. Thanks Matthias
Sorry folk, under 0.9.1 it still don't work! Just found out that I can't resize the pop-ups either - is this a bug or a 'feature'? I know that through JavaScript you can define the size of the window, but does this mean I can't change it? Oliver Tupman.
Reporter: Have you a URL ?
Just realised something - the pop-up window will move between screens if Mozilla is NOT maximised. Here's a page I just set up to demo the bug: http://www.dts-workshop.com/mozilla-bug.html If I have Mozilla maximised, the pop-up window does not display on the second monitor. The cursor is displayed where the window 'should' be, but there's no window.
-> xpapps, anyone have a 2 monitor setting
Assignee: asa → pchen
Component: Browser-General → XP Apps
QA Contact: doronr → sairuh
unfortunately, i don't have a 2-display setup. :(
Keywords: qawanted
We might need a relnote on this if we can't find anyone else with a dual display.
Keywords: relnote
Oh, yeah. Reporter: Can you provide us with more information on any dual-display software or hardware you're running? e.g. video card make and model, driver version number.
Had a look at this using the TV Out on my GeForce2MX with Twinview. Granted, it's not a "dual monitor" setup, but it's a WFM with the following configuration: GeForce2MX w/TV out Monitor on VGA out, TV on TV out Windows NT 4.0 nVidia reference driver 12.41 Twinview enabled using "Horizontal span" setting (TV is effectively a 2nd monitor). Build 2001072003 Page provided by reporter.
Marking NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
-> danm
Assignee: pchen → danm
Keywords: helpwanted
Target Milestone: --- → Future
QA Contact: sairuh → paw
Blocks: multimon-win
WFM: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040802 Firefox/0.9.1+ Using dual monitors and a Matrox G450 Can anyone reproduce this bug with a nighlty build?
Product: Core → Mozilla Application Suite
The following bugs all seem to be related and/or duplicates: Bug 78155, Bug 149479, Bug 232690
Microsoft Word 2000 suffers the same problem with opening new windows! That is: Open MS Word and place on secondary display monitor. Choose Edit > Find The "Find and Replace" Window opens on the primary monitor. This suggests to me an OS problem.
Bug 245418 describes a Mozilla bug opening popup menus on the wrong monitor under some conditions, but not all. And AFAIK these days Mozilla in general opens new windows on the same monitor as the opener window (though I'm prepared to believe it could have trouble with maximized windows). So I don't think there's an OS problem, at least not one that can't be worked around. However I don't have a multiple monitor system anyway and haven't for a long time. I have to let this bug loose for someone else to take a look.
Assignee: danm.moz → nobody
Summary: Pop-up windows (via JavaScript, etc.) will not display on my second monitor → maximized pop-up windows (via JavaScript, etc.) will not display on my second monitor
Target Milestone: Future → ---
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.