RFE: Bring back former behavior of Go menu.



13 years ago
13 years ago


(Reporter: dfe, Assigned: mikepinkerton)





13 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050914 Camino/1.0a1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050914 Camino/1.0a1

The original Camino Go menu contained only entries for the active window (or
active tab within the active window).  It was a simple list having the
forward-most page on top and the first page viewed in the window on the bottom
with the currently-viewed page checked.

While I realize this is available by holding down the back or forward button
(depending on which way you want to go) I found the Go menu to be easier to use.
 Unfortunately, it broke completely when running Camino on Tiger and subsequent
releases of Camino have removed the feature entirely and replaced it with the
more traditional Go menu (as found in Firefox with the name Go and Safari with
the name History).

I recommend that the Go menu as it is now in Camino be renamed to History
(consistent with at least Safari) and the Go menu as it was be put back.

Reproducible: Always

Steps to Reproduce:

Comment 1

13 years ago
Sorry, we made a conscious decision to put global history on the Go menu. It's
more useful to most users.
Last Resolved: 13 years ago
Resolution: --- → WONTFIX

Comment 2

13 years ago
I'm sure it was a concious decision but is there any chance that both could be
made available?  Having both Go (per-window) and History (global) could work.

The old Camino per-window go menu obviously doesn't make sense on other
platforms as it would be just as easy to reach the Back or Forward buttons.  On
the Mac I find it works quite well though as I can quite swiftly move the mouse
pointer to the menubar where the go menu is always in exactly the same location.
 The back and forward buttons are never in the same place but the Go menu always is.
You need to log in before you can comment on or make changes to this bug.