Closed Bug 61156 Opened 24 years ago Closed 23 years ago

Inconsistency in editor-related menu items (edit page vs edit link in composer)

Categories

(SeaMonkey :: UI Design, defect, P4)

Product:
SeaMonkey
Component:
UI Design
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED INVALID
Milestone:
mozilla0.9.8

People

(Reporter: bugzilla, Assigned: marlon.bishop)

References

Details

Navigator's File menu says "Edit Page", while the context menu for a link 
says "Edit Link in Composer".  Why does the user know where he's editing the 
page when he uses the File menu, but not the context menu?
Composer is the name of the editor -- the File menu does not contain a complete
description, as in "Edit Page in Composer." Due to constraints in the strings
used for menus.
"Edit Page in Composer" is one character longer than "New Navigator Window" 
(another item in the File menu), but appears slightly shorter in a 
variable-width font.  Is there a hard-coded character limit that affects only 
static menuitems that aren't part of context menus?
Summary: Inconsistency in editor-related items → Inconsistency in editor-related menu items (edit page vs edit link in composer)
well, actually this is not editor, this is menus in navigator
Assignee: beppe → asa
Component: Editor → Browser-General
QA Contact: sujay → doronr
over to XPApps GUI Features.
Assignee: asa → ben
Component: Browser-General → XP Apps: GUI Features
QA Contact: doronr → sairuh
Context menu cleanup, & easy.
Status: NEW → ASSIGNED
Priority: P3 → P4
Target Milestone: --- → mozilla0.9.7
Depends on: 75338
Giving to UE for thoughts.
Assignee: ben → marlon
Status: ASSIGNED → NEW
moving to 0.9.8
Target Milestone: mozilla0.9.7 → mozilla0.9.8
"edit link in composer" menu item has been removed according to the latest
context menu spec.  so this bug is no longer valid
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
zap.
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
Component: XP Apps: GUI Features → UI Design
You need to log in before you can comment on or make changes to this bug.