This question already has an answer here:

This question is not specific to language/framework/platform.

I want to know (and confirm), what should happen (by default) if a user taps and holds (or clicks and hold).

This is more about basic usability and user experience.

What would a user expect to happen if the user taps(or click) and hold.

For some clarification I did read this: https://msdn.microsoft.com/library/windows/apps/br208928

The framework where I need to work on currently triggers holdstart if you hold for more than 400ms, and that in turn triggers tapcancel. I am not happy with it, thus want to know what is the more appropriate default behavior a user would expect.

marked as duplicate by Mayo, SteveD, Devin, Graham Herrli, JohnGB Nov 21 '16 at 11:45

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 1
    FWIW, a tap-and-hold would not behave the same as a click-and-hold. The conventions used in touch-only devices are quite different than a desktop experience. – maxathousand Oct 19 '16 at 14:07

Material design simply says:

Example: Select an element, such as a list item

Long press is not used to display a contextual menu.

I couldn't find guidelines for iOS IXD but I did find a page about 3D Touch that seems to show it being used for a contextual menu and a 'quick peek' feature.

Not the answer you're looking for? Browse other questions tagged or ask your own question.