783767 - Draggable content vs clickable content

Status: UNCONFIRMED

(Core :: Disability Access APIs, enhancement)

Description

[another_sam]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:15.0) Gecko/20100101 Firefox/15.0
Build ID: 20120726134955

Steps to reproduce:

This just happened to my mother while browsing. On a link image (<img> element inside <a> element):
1. Mousedown on the link
2. Accidental drag of something between 15 and 20 pixels
3. Mouse up


Actual results:

1. The image inside the link was dragged a few pixels and dropped to the same place it was.
2. The link was not effectively clicked, and she though it was, and the picture carousel she was supposed to pause kept moving on, to her frustration and confusion.


Expected results:

1. The image is not dragged.
2. The link is effectively clicked.

Back in my PC, examining the behavior of Firefox in this situations, I see that it already allows for a bit of accidental dragging. So I'd conclude that what should be done is increasing that margin of error a few more pixels. Up to 20 at least.

The main pro is obvious. Now I guess the main con is more dragging effort and potentially more confusion for voluntary fine-dragging scenarios. Being those the main two forces to balance, those 20-25 pixels still seem to me a good choice.

Comment 1

[Mats Palmgren (inactive)]

> Accidental drag of something between 15 and 20 pixels

I think that's very rare for most users.

> the main con is more dragging effort and potentially more confusion
> for voluntary fine-dragging scenarios

I think the main con is that the drag gesture wouldn't give feedback
until later than normal for the platform, causing confusion about
why Firefox behaves differently.

I don't think we should change the default to 20-25 pixels to start
a drag operation - it might make sense as an accessibility feature
though.

-> A11y