Closed
Bug 133845
Opened 23 years ago
Closed 22 years ago
multiple monitor incorrect menu url bar placement
Categories
(SeaMonkey :: Location Bar, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 138933
People
(Reporter: ellisteer_box8003, Assigned: hewitt)
Details
When opening the drop down history on the URL bar while in dual monitor mode the
box containing the URL's is incorrectly split between the two screens (centered
on the larger virtual screen) when Mozilla is anywhere on the second extended
screen. The URL bar is correctly layed out when Mozilla is on the primary
screen. System uses a single video card.
This does not occur on a similar system using Windows 2000 and two video cards.
| Reporter | ||
Updated•23 years ago
|
Summary: dual monitor url bar placement → multiple dual monitor url bar placement
| Reporter | ||
Comment 1•23 years ago
|
||
This may be related to bug 33438 where Javascript returns a screen width which
is the sum of all monitors.
Bug was filed on build 2002031104
| Reporter | ||
Updated•23 years ago
|
Summary: multiple dual monitor url bar placement → multiple monitor url bar placement
| Reporter | ||
Comment 2•23 years ago
|
||
This also does not always occur on XP, working on figuring out what triggers
this state.
Comment 3•23 years ago
|
||
WFM too, JRE 1.4, WinXP and Mozilla build 2002060406.
Mark it as WFM
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Comment 4•23 years ago
|
||
Made a mistake while handling some bugs reports :-/
Reopen it :-)
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 5•23 years ago
|
||
On my WinXP SP1 laptop using a Mobile Radeon 7500 chipset to drive both the
panel and a monitor as separate screens, I see this behavior with the 1.1
release. In fact, not only is the history list appearing right-justified on the
first monitor, the menu code is also drawing all of the menus at the edge of the
first screen, rather than below the menu bar.
Comment 6•23 years ago
|
||
More instructions:
I'm reproducing this using the 1.2a drop 2002091014.
It only happens when I start Mozilla while my laptop is mobile (and only has one
screen), and then dock the laptop and activate the second screen. After
"extending my desktop" from the Windows Appearance control panel, I can now drag
my Mozilla Navigator window to the second monitor and get the odd history,
popup, and menu bar effects.
| Reporter | ||
Comment 7•23 years ago
|
||
-confirming bug
-noting that reporter's system was laptop
-expanding summary
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: multiple monitor url bar placement → multiple monitor incorrect menu url bar placement
Comment 8•22 years ago
|
||
I can report the same bug on my multiple monitor setup. I also have the
Mozilla source on my machine. I can help you debug this if you give me some
hints. What routine calculates: where should I drop down the menu list?
Comment 9•22 years ago
|
||
I see similar behavior when my screen resolution is changed in XP. I start in a
dual-monitor 1600x1200 configuration, and everything works fine. When I
relocate and use Remote Desktop (which brings everything onto a single 1024x768
screen), Mozilla seems to continue working OK. When I move *back* to the
dual-monitor 1600x1200 configuration, Mozilla confines all of its menus and
pop-ups (e.g. tool-tips) to an area 1024x768 in size anchored at the top left of
monitor 1. In short, it doesn't seem to realize that the available screen size
has increased and continues to confine its menus and the like to the resolution
and monitor it remembered.
Restarting Mozilla clears up the problem. This doesn't just affect the URL Bar,
it affects all menus and similar UI non-dialog pop-ups. I don't have a laptop.
This may or may not be the same bug. I'm using Mozilla/5.0 (Windows; U;
Windows NT 5.1; en-US; rv:1.3) Gecko/20030312.
Comment 10•22 years ago
|
||
related to bug 138933 ?
| Reporter | ||
Comment 11•22 years ago
|
||
They look to be the same. Going to dup this against it.
*** This bug has been marked as a duplicate of 138933 ***
Status: NEW → RESOLVED
Closed: 23 years ago → 22 years ago
Resolution: --- → DUPLICATE
Updated•17 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•