Vincent Baaij
May 18, 2018
  1813
(3 votes)

Editing on a touch screen device

Working with a touch screen device, like a Surface Pro, Book or Laptop, might lead to some unexpected behaviour in the editor. In my case, I didn't receive any feedback on hovering the cursor over the editable parts of a page or block. So, no green (or grey on a content area) highlight and no information label with the field name. It didn't matter what browser I tried it in. Edge, Firefox and Chrome all gave me the same feedback-less experience.

It took some digging around to find out what caused this. I consulted developer support, but for them it was working as expected. I uninstalled all browser extensions/add-ons, but still no success. Then I moved to the browser specific settings. Turns out all the browsers have W3C Touch API support that you can change. After disabling this support all browsers started to show the expected highlight and label!

If you happen to have the same problem on a touch screen device, here's how you can change the mentioned setting:

Edge

Navigate to 'about:flags'. In the screen that appears scroll down to Standards Preview. For 'Enable touch events' select 'Always off' in the dropdwn list.

Image EdgeTouch.PNG

Firefox

Navigate to 'about:config'. In the screen that appears serch for 'touch_events'. Double click and set the value to '0'

Image FirefoxTouch.PNG

Chrome

Navigate to 'chrome://flags'. In the screen that appears look for 'Touch Events API'. Set value to 'Disabled'

Image ChromeTouch.png

Hope this helps,

Vincent

May 18, 2018

Comments

Erik Henningson
Erik Henningson May 19, 2018 07:38 AM

This is what I do:

Check "Limit touch support" on my users´s settings

Vincent Baaij
Vincent Baaij May 22, 2018 09:42 AM

Good catch Erik! Thanks.

That is indeed a lot easier to set and you don't mess with other sites that might depend on the original API support. 

Please login to comment.
Latest blogs
Opti ID overview

Opti ID allows you to log in once and switch between Optimizely products using Okta, Entra ID, or a local account. You can also manage all your use...

K Khan | Jul 26, 2024

Getting Started with Optimizely SaaS using Next.js Starter App - Extend a component - Part 3

This is the final part of our Optimizely SaaS CMS proof-of-concept (POC) blog series. In this post, we'll dive into extending a component within th...

Raghavendra Murthy | Jul 23, 2024 | Syndicated blog

Optimizely Graph – Faceting with Geta Categories

Overview As Optimizely Graph (and Content Cloud SaaS) makes its global debut, it is known that there are going to be some bugs and quirks. One of t...

Eric Markson | Jul 22, 2024 | Syndicated blog

Integration Bynder (DAM) with Optimizely

Bynder is a comprehensive digital asset management (DAM) platform that enables businesses to efficiently manage, store, organize, and share their...

Sanjay Kumar | Jul 22, 2024

Frontend Hosting for SaaS CMS Solutions

Introduction Now that CMS SaaS Core has gone into general availability, it is a good time to start discussing where to host the head. SaaS Core is...

Minesh Shah (Netcel) | Jul 20, 2024

Optimizely London Dev Meetup 11th July 2024

On 11th July 2024 in London Niteco and Netcel along with Optimizely ran the London Developer meetup. There was an great agenda of talks that we put...

Scott Reed | Jul 19, 2024