This is another one of those "we've been talking about it forever, but never filed it" bugs. We should eliminate the use of click-hold for accessing the session history menus on the back and forward button. It's not discoverable, it's inconsistent with the rest of our UI and with the OS, and, because of all those, ends up being hard to use. Fortunately, Wevah knows how to do this; I think it involves drawing with NSButtonCell (but maybe I've just been reading too many of Colin's form widget bugs...) so that we have two distinct hit targets.
I think getting rid of the click-and-hold is a great idea, but I think making two distinct targets might possibly suck (largely because one of them is going to be RIDICULOUSLY small). cl
the change in behavior that you describe seems to have been implemented in FF3, much to my dismay.
This is a Camino bug, not a Firefox bug, and we share neither implementation nor UI decision-makers for the toolbar.
Let me elaborate then... I use both Camino and Firefox. This change was introduced to FF3, and I do not like it. That dislike of the idea in practice is the core of my point here, as a "vote" against this idea being implemented in Camino. I like a clean UI. I do not need a down-arrow (or any other secondary click target) to tell me that there is an expandable menu, it wastes screen space permanently compared to the singular loss of time figuring out how the feature works without it.
This bug has been buried in the graveyard and has not been updated in over 5 years. It is probably safe to assume that it will never be fixed, so resolving as WONTFIX. [Mass-change filter: graveyard-wontfix-2014-09-24]
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.