This illustrates that what is stable across different UIs is the
relative ordering of the event triggers, not exactly what they
are triggered by.
Something that is kicked off by waving the mouse by something is
the lightest touch.
Something that is kicked off by a single click is the next
heaviest touch -- more like you mean it, can be used for more
serious consequences.
Something that is kicked off by a double-click is the heaviest
touch of all in this progression. It is used for things that
you really think about before doing.
double-click -to- click -is-like- confirm-before-do -to- just-do-it
Al
to follow up on what Charles McCathieNevile said:
> I came up with an illustration:
>
> in IE and Navigator, a single click corresponds to onActivate (my
> hypothetical - a wish-list item) and a double click has no normal behaviour.
>
> in Amaya, where browser and editor are together, a single click moves the
> insertion point (and the focus?) and a double click activates. In which
> case a double click should fire an onActivate event, and a single click
> an onFocus event.
>
> Charles McCN
>