Closed
Bug 200249
Opened 21 years ago
Closed 21 years ago
Order of context menu should always be the same
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
People
(Reporter: gbrinkmann, Assigned: hyatt)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030306 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030306 IMHO it is not an user friendly design that the order of the items in the context menu change from context to context. For example: Why is "Back" not always the first item in the menu? It would be much more simple to handle the back function if you can rely on the back item to be placed in the first position. (Why does a user have to know if the page is built with frames or not to find the back-menu-item?) Also the "back" button should always be present. When you have selected some text or the mouse pointer is about an image you currently cannot go back using the context menu. Special things that regard on the context (e.g. copy&paste, etc. in the selection-context or "View Image" in an image context or frame-things in the frame context) should always be placed in the same part of the menu (just separated by horizontal line delimiters from the general menu items) or alternatively (and better) in submenus as it is done for "This Frame". The same question not only for the back item but also for "Page Source", "Page Info" and all the others that you cannot find in an selection- or image-context. The resulting menu structure would be (on a page with frames which has an backgroundimage, about an image and in the case of an selection, all at the same time): Back Forward Reload Stop -------- This Page >> This Frame >> This Image >> This Background Image >> This Selection >> The contextual Submenus (all starting with "This " here) can contain their special items then. Perhaps some very often used items could still be placed in the main menu. For me it was "Page Source", "Page Info", "Frame Source", "Frame Info". It also would be great to have one "This Frame (framename)" submenu for all frames in the current page. With this you can have access to a frame that contains another frameset (multiple nested framesets) that you cannot access at the moment AFAIK. (Try to view the source of such a hierarchical middle frame with a current browser) Reproducible: Always Steps to Reproduce:
Comment 1•21 years ago
|
||
ARGH. This is why we shouldn't have added even the "frame" submenu -- a submenu in a context menu makes things very difficult and slow to get to, eliminating much of the usefulness of a context menu...
Whiteboard: DUPEME
Comment 2•21 years ago
|
||
->menus
Assignee: asa → hyatt
Component: Browser-General → XP Toolkit/Widgets: Menus
QA Contact: asa → shrir
Comment 3•21 years ago
|
||
*** This bug has been marked as a duplicate of 27338 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Component: XP Toolkit/Widgets: Menus → XUL
QA Contact: shrir → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•