782679 - [ux] Define selection / tap behavior for touch input in metrofx

Status: RESOLVED FIXED

(Firefox for Metro Graveyard :: Input, defect)

Description

[Jim Mathies [:jimm]]

cc'ing the ux team. Here is a prelim. guess at how this should work. I'm going to be working on selection behavior this week and next, so I'd like to get this nailed down.

Tap:
---------------
1) if pan is not active, on *text* that is not selected and can not receive focus, select underlying text and apply selection markers.
2) on existing selection, copy content, clear selection, and display some sort of visual "copied" feedback
3) on focusable elements, set focus

Long tap:
---------------
Win8 provides a animated target square for this interaction. If you tap and hold until the square is fully visible then release a long tap event is generated.

1) on text that is not selected, select a portion of the underlying text and display selection markers.
2) on existing selection, bring up context menu.

Double tap:
---------------
1) any where in content - smart zoom. Currently doesn't work on Win8 due to bug 766142.

Tap & drag:
---------------
1) pan content / highlight menu items / etc.
2) if initiated on a selection marker, drag marker to appropriate location.

Comment 1

[Jim Mathies [:jimm]]

This is mostly ux interaction related. It was originally filed as a seeking input bug.

Comment 2

[Yuan Wang(:Yuan) – Mobile Firefox Design Lead]

The behaviors mentioned above make sense to me.

Currently, the context menu pops up from the top right top of your touch selection.
The space in between the selection and context menu is about 0.8 inches, almost the same width as a finger.

My one suggestion is to make the context menu feel like it's attached to the touch selection. Once long tap is released, the context menu pops up on top of the selection with no space in between.


Let me know if there is anything else that needs UX input.