Christopher Jahn wrote:
>
> And it came to pass that Warren Bell wrote:
>
> >Christopher Jahn wrote:
> >>
> >> And it came to pass that Warren Bell wrote:
> >>
> >> >Christopher Jahn wrote:
> >> >>
> >> >> And it came to pass that Warren Bell wrote:
> >> >>
> >> >> > I don't know if this is a bug or somone actually meant
> >> >> > it to be this way but why would you have the right
> >> >> > click context menu execute on the release of a right
> >> >> > click? One of the things I like about Netscape 4.x is
> >> >> > you can right click and hold, scroll down to your
> >> >> > selection and let go and the function gets executed.
> >> >> > Now you have to right click, let go, scroll and left
> >> >> > click to do somthing. It reminds me of IE.
> >> >> >
> >> >>
> >> >> This is the way it has always worked for me.
> >> >
> >> >I can't see how this would be better in any way. Seems
> >> >like it goes against useability..
> >>
> >> Except that it DOESN't. It's perfectly usable, and it
> >> behaves like every local menu I've ever used:
> >> - right click release: menu appears
> >> - scroll
> >> - Left click executes
> >
> >Have you ever used Unix? Context menus popup on right mouse
> >down. I know we're talking about Mozilla on windows, but
> >would it hurt to have it popup on mouse down? It didn't hurt
> >Netscape.
> >
> >> This is certainly how Netscape has behaved since I've been
> >> using it.
> >
> >Netscape works both ways. And it _is_ easier to
> >click-drag-release; it's all one motion, easier to use.
> >
> No, it's NOT. It might be easier FOR YOU.
> It is NOT easier for ME.
>
Then maybe it would be a good idea to have a
user_pref("context_menu_on_release", false) like Jay suggested. That
would give people a choice between IE style and the way everything else
does it.
