179745 - (DualForURL) Dual headed setup with browser on secondary display handles URL history wrong

Status: RESOLVED WORKSFORME

(SeaMonkey :: Location Bar, defect)

Description

[bart]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0

Hardware: Matrox Milennium G450 Dual Head video card, 21 inch IBM P201 monitor,
15 inch IBM P50 monitor.

Recreation: Configure syststem to use the dual head setup. Move the Browser over
to the secondary display.  Click the drop down box for the URL history.  The URL
history is displayed on the primary display instead of on the same display as
the application.  The problem is also apparent when Auto-history feature
displays the URL history when you type in an URL you have visited before.

Solution: Move the URL history over to the same display as the browser.



Reproducible: Always

Steps to Reproduce:
1. Configure syststem to use the dual head setup.
2. Move the Browser over to the secondary display.
3. Click the drop down box for the URL history.

Actual Results:  
The URL history is displayed on the primary display instead of on the same
display as the application.

The problem is also apparent when Auto-history feature displays the URL history
when you type in an URL you have visited before.


Expected Results:  
Move the URL history over to the same display as the browser.

Comment 1

[R.K.Aa.]

same was reported in bug 148846, but 1.0.1 is too old to report bugs against.
(See the bug-reporting guidelines) Can you reproduce the bug with a recent build?

Comment 2

[bart]

Sorry for the duplicate.  My initial searches didn't pull anything up.  The
newest build resolves this problem.  It also seems to resolve an issue I had
with the browser window always popping up on the primary display instead of the
one where I closed it last.  Moving it back over was becomming annoying.  

Comment 3

[R.K.Aa.]

Resolving as WFM per comment 2. Thanks for the quick feedback!