Closed Bug 228021 Opened 22 years ago Closed 22 years ago

The menus are opened always on the primary screen.

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Thunderbird0.5

People

(Reporter: lemm.be, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031209 Firebird/0.7+ (scragz) Build Identifier: Mozilla Thunderbird 0.4 (20031206) When Thunderbird is displayed on the secondary, all the menus are opened on the primary screen. Reproducible: Always Steps to Reproduce: 1.Run a multiple screen system. 2.Run thunderbird on the second screen. 3.Open File menu or other (right-click too). Actual Results: The menu are opened on the primary screen. Expected Results: The menus are opened in their places
This bug does not appear any more in the version Mozilla Thunderbird 0.5a has (20031211).
great
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird0.5
This happens to me on OSX.3.2 on all the builds so far this year as far as I can tell.
I'd like to reopen this bug because this happens for me with my monitor configuration with Thunderbird 1.0.2 (20050317) on Windows XP. 1. No monitor attached 2. I open Thunderbird (opens on primary monitor) 3. I attach my second monitor (using Windows Display Properties I move the second monitor to the left of my primary monitor i.e. -1280,0) 4. I move Thunderbird to my external monitor (drag to the left) 5. Thunderbird menus open at left-most point of primary monitor Issue does not occur when I attach the monitor before opening Thunderbird. I image it's something to do with the -1280 deal where Windows resets the coordinates of all existing open windows when a new monitor is attached. Somehow Thunderbird freaks out when this is a negative adjustment (i.e. new monitor attached to the left of the primary monitor). Can send screenshots or more information if anything else is needed.
You need to log in before you can comment on or make changes to this bug.