229326 - Enabling 2 monitors requirres restart of mozilla

Status: RESOLVED DUPLICATE of bug 255551

(SeaMonkey :: General, defect)

Description

[Alexandre Gomes]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208

When we have mozilla open and if we go to control panel and enable the second
monitor to expand the desktop wew got this:
- tooltips, menus, and the autocomplete always in the primary monitor (Even if
mozilla is in the second!!!)
- If we close it and then open it again the problem is solved if we put the Full
window of mozilla in one of the monitors. If we let a half in one monitor every
thing happens again (shows in primary monitor)

Reproducible: Always

Steps to Reproduce:
1. Open mozilla with monitors in mirror mode
2. Enable non-mirror mode
3. move the window to secund monitor
4. Go to anny menu... write in the url textbox etc...

Actual Results:  
shows things in the wrong monitor

Expected Results:  
improve the method of using coordinates enabling it to work in multiple monitors.

Comment 1

[R.K.Aa.]

*** Bug 249742 has been marked as a duplicate of this bug. ***

Comment 2

[R.K.Aa.]

dependant on bug 62395?

Comment 3

[Scott Eade]

I can confirm that this occurs in FireFox 1.0 Preview Release.

There seem to be quite a number of open dual monitor issues.  It would appear
that mozilla/firefox needs to arrange to be notified when the monitor
configuration changes and then recompute the monitor characteristics in a
similar fashion as is done at startup.  Doing this would probably kill off quite
a few of the outstanding issues.

In the mean time it is helpful to know that restarting after switching to dual
monitors seems to fix several of these issues.

Comment 4

[Robin Monks]

Duping to similar Bug 255551.  Reporter, if you feel this was done in error,
please REOPEN.

*** This bug has been marked as a duplicate of 255551 ***

Comment 5

[Alexandre Gomes]

No problem at all, but my bug report is much older than the other one. The other
bug should had been mark as duplicate of this...