Closed Bug 15091 Opened 25 years ago Closed 25 years ago

Menus display only to the right, will go offscreen...

Categories

(SeaMonkey :: MailNews: Message Display, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 9454

People

(Reporter: laurel, Assigned: mikepinkerton)

References

Details

Using 1999092809m11 on linux 6.0, NT 4.0 and mac OS 8.51 Menus will only display to the right and will not adjust leftward if running off the edge of the sreen. A great example: When using the File/Copy message hierarchichal menus, submenus will run offscreen to the right. This can happen if you have several sublevels of folder structure(s) or if the window is in a restored state and moved so the menu starts cascading to the right edge of the screen. In all platforms in 4.x, the (sub)menu which can not be fully displayed to the right within the current screen viewing area will adjust and display to the left so the user can see the full menu display. 1. In messenger window, open Inbox and select a message. 2. Resize window and move it so the main menu item Message is fairly close to the right edge of the screen. 3. Pull down the Message menu and select Move Message or Copy message. Result: The menu runs offscreen to the right, hiding some or all of contents. Particularly hard to deal with if you're using Move or Copy with a large subfolder hierarchy.
QA Contact: lchiang → laurel
Oops, mistake ... doesn't happen on the mac, just windows and linux.
Assignee: phil → saari
Reassign to saari
Status: NEW → ASSIGNED
Target Milestone: M11
Blocks: 11091
mailnews area so adding to our tracking bug.
Priority: P3 → P1
CCing Pav
Assignee: saari → pinkerton
Status: ASSIGNED → NEW
Pink is owning XPmenu positioning issues, as per the architecture meeting (see what happens when you don't come to these pink)
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 9454 ***
Status: RESOLVED → VERIFIED
Marking verified as duplicate.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.