• hgap

    (@hgap)


    Long press on touch screens reveals the context menu – when not disabled.

    Disabling long press does not work when iPhone/iPad (+others?) are in desktop mode. – Please help!

    Best regards

    Karsten Pagh

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Jasmine

    (@hyenokian)

    Dear @hgap,

    Thanks for the topic.

    In order for us to be able to help you, please provide more details about the issue, including screenshots or a short video if possible, so that we can better understand what you’re referring to.

    Looking forward to hearing back from you.

    Thank you.

    Thread Starter hgap

    (@hgap)

    OK, I’ll try to explain in some more detail:

    Without Secure Copy Content Protection and Content Locking the context menu appears on right click on desktop. On mobile/tablet the context menu appears when holding a finger for more than app. on second (long press).

    Secure Copy Content Protection and Content Locking should disable the context menu on desktop and on touch screen devices. This works fine on desktop devices – on touch screen devices it only works when the browser settings requests the mobile version of the website. If the browser is set to request the desktop version, the context menu appears by “long press”.

    Example: Chrome browser on iPhone. By tapping the three dots in lower right corner a menu appears. One of the menu points allows the user to set up the browser to request either desktop or mobile version of the website.

    Plugin Support Jasmine

    (@hyenokian)

    Dear @hgap,

    Thanks for the reply and thanks for the clarifications.

    We have checked and noticed a problem in this regard.
    Please contact us via?this form?so we can review your request and provide a?fixed zip file as soon as possible.

    If you have any other questions, feel free to open another topic.

    Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.