Closed
Bug 148561
Opened 22 years ago
Closed 22 years ago
Context menu for URL/link in mail/news has two line separators the first time
Categories
(SeaMonkey :: MailNews: Message Display, defect)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
CLOSED
DUPLICATE
of bug 148078
People
(Reporter: djst, Assigned: sspitzer)
Details
From David Tenser (david.tenser@telia.com):
BuildID: 2002060108
When right-clicking a link in mail/news, the context menu looks like this:
-
Open Links in New Window
---separator---
---separator---
Copy Link Location
---separator---
Save Link Target As...
Bookmark This Link
-
After the first try, it looks as it should look:
-
Open Links in New Window
---separator---
Copy Link Location
---separator---
Save Link Target As...
Bookmark This Link
-
Reproducible: Always
Steps to Reproduce:
1. Make sure mail/news is closed and then start it
2. Right-click a link in the start page (or any email containing a link)
Actual Results: There are two menu separators under the "Open Links in New
Window" menu item the first time you right click a link.
Expected Results: There should be only one menu separator.
Comment 1•22 years ago
|
||
worksforme (Linux, 2002052421)
I see the same as reporter on a current CVS build, Linux, but only the first
time i right-click a link. Right-clicking a mailto shows one extra separator on
top of menu - regardless.
Separators in mailnews context menus seem to have multiplied all over lately:
bug 148078
Possibly related to fix for bug 138826
Comment 3•22 years ago
|
||
ah.. this time it comes. You need to restart Mozilla at all to see it again. New
Build btw.: 2002060107
Assignee | ||
Comment 4•22 years ago
|
||
is this a trunk build, or a rc3 / mozilla 1.0 build?
Assignee | ||
Comment 5•22 years ago
|
||
*** This bug has been marked as a duplicate of 148078 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
verified dup, I remember this bug.
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•