On 13 Nov 2008, at 09:09, Jackson Fox wrote:
[snip]
I think there are some cases where we *can* treat hovering as a
declaration. In particular, I'm thinking of uses such as Netflix's
movie info boxes. When a user places a mouse over an active object,
and then pauses without a click, I think it's a reasonable inference
that the user is lacking information to move forward.
[snip]
As ever - it depends :-)
If the page has enough content that the user needs to pause to
comprehend it, and enough area of the page containing active links,
then the chance of "accidentally" firing off with a hover affect can
be quite high.
I saw exactly this behaviour this a while back when I did some testing
on a site where the content area and side bar contained a number of
links that gave a preview of the following page.
The user paused to read content - with the pointer over a preview area
purely by chance. A couple of seconds later preview-layer appeared.
User gets distracted - moves cursor enough to get the preview layer to
vanish. User resumes reading - accidentally leaving cursor over
_another_ preview link...
This sometimes happened two or three times in a row until the user
threw the cursor to a screen edge.
Fun :-)
Adrian
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [EMAIL PROTECTED]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
