Site logo

Archived topic

Double click needed for links in chrome on ios

8 replies · Started by Kees on November 29, 2022

Viewing posts 1–9 of 9

Hello,

I have the problem that I need to double click on links in Chrome on iOS devices for them to work. I know of the 'disable back to top button hack' and of disabling the sticky navigation (hide-on-scroll). I saw those solutions in another post. Both are disabled, but that doesn’t solve the problem. Do you know what else it could be?

Thanks in advance.

Roy

Hi Roy,

David and I both tested on iPhone, but it doesn't seem to have the double click issue.

Have you tried using another device?

Let me know!

Hi Ying,

I'm using an iphone 13 pro, its not 100% always but maybe 90% or something. For example this url: https://www.lekkeretenmetlinda.nl/lunch-recepten/ If you scroll down to the first post, often I have to click twice. Ik had this problem before and could fix it with disabling the back to top button and that worked in that case, but now I don't know whats the matter.

So i'm using iphone 13, chrome, incognito mode.

Roy

If it helps: I made some screenrecordings which I can send you if possible.

For some background. the issue with sticky nav and back to top is related to Chrome iOS changing focus when elements enter the viewport ( eg. sticky nav or back to top ) after the screen is initially rendered. Its something Tom picked up on, during one of the many head banging trials we have performed.

I think you may be experiencing the same issue as there are late loading elements on that page.

If you have a screen recording it would be useful to see - you will need to share a link to the cloud folder / media library the video is saved in.

Hi David,

thanks for your explanation. I added the download link in private.

Roy

Hi Tom,

it works but it comes with some other visual changes as well. It places outline/borders on some elements (in the offcanvas menu for example). Also mobile hover effects after clicking something don't work anymore.

Roy

Yea, makes sense there would be some tradeoffs.

As of right now, it seems to avoid this particular iOS bug it's important to make sure nothing appears/disappears from your pages after the initial render.

This archived topic is closed to new replies.