"Michael Winter" <M.Winter@blueyonder.co.invalid> wrote in message news:<opsep8lkuox13kvk@atlantis>...[color=blue]
> Easier for whom?
>[color=green]
> > It saves the user a step.[/color]
>
> It saves some users a step. It causes others to take many.
>[color=green]
> > What sort of problems come up? Why is it bad?[/color]
>
> It's bad for disabled users. Before you think, "That doesn't apply to my
> site", the issue covers a wide range of people, not just some preconceived
> subsection. People with cognative, visual, and motor disabilities can all
> be affected.
>
> Users associate behaviour with controls. A user doesn't necessarily expect
> selecting a value from a drop-down list to actually perform an action such
> as navigation. Usability studies show that this has many effects on users;
> none of them positive.
>
> Number 3:
> <URL:http://www.useit.com/alertbox/990530.html>
>
> Despite being six years old, every point in the article still holds true.
>
> In addition, a user might not be able to see all of the options. This
> might cause them to select a value that appears to be the closest. If they
> then discover the actual destination, they'll try to select it, but it
> will be too late; the request has already started and scripting is usually
> ignored at that point. What's worse is that if they go back, the option
> they selected just before changing pages might be selected. As most
> drop-down navigation menus use the change event, they'll have to select a
> different value before they can select the required one. Of course, most
> people won't know that.[/color]
The very good, well respected weblog Crooked Timber uses onChange() as
their firing point for moves after you've picked a category in a
select box:
http://www.crookedtimber.org/archive..._politics.html
Scroll down and you'll see the selectt box for categories on the left.
I'm not sure if this is the default for MoveableType, which is also a
much respected bit of software.
Usage is whatever major sites do. I imagine their designer thought, as
I did, that not having a "Go" button would save the user a step.
Nevertheless, for now, I'm doing it the way you suggested (unless the
client complains), as you can see on the left side of this page:
http://www.alexmarshall.org/index.php?pageId=2494