Re: Nav links in context menu

On Mon, 2003-07-28 at 08:22, Tommi Komulainen wrote:
> On Mon, 2003-07-28 at 00:51, Crispin Flowerday wrote:
> > The main problem with them is that the menu when an image is also a link
> > is already large and adding the navigation as well makes it huge. tko
> > suggested only adding the back button, but I felt that only adding one
> > of the nav items would make it inconsistent, which is probably worse
> > than have huge context menus.
> 
> I was suggesting adding only the Back button in all of the menus, and
> always at the same position (first)  

I'd really hate if link contexts had Back on top.

> The reasoning being, does anyone
> ever really use Forward at all?  (not limited to context menu) 
> Similarly for the Reload button, does anyone really use it from the
> context menu?

When I am not using the keyboard I am used to navigate using exclusively
the context menu. This includes Back, Forward, Reload  and in the good
old days of galeon 1 - Up, back/forwdard/up history on the
back/forward/up context. In my ideal galeon 1 setup the menubar was
hidden and the only nav item on my toolbar was Stop.
As someone else pointed the pointer trip to the toolbar is a pretty
tedious task which just hurts my wrists and breaks the natural flow of
things.

Also for me the "Open image" as first item context on images seems to be
pretty pointless and rarely of some use.


Regards
Yanko



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01