This topic contains 3 replies, has 2 voices, and was last updated by 
- Posts
Hi Ernest,
so soon we speak again. Hope this one is a short one.
At the URL above I place my AJAX search form to an empty element in my mobile menu when below 1024 px. That works well on desktop, but each time I tap into the search field on mobile it loses focus, i.e. I cannot type at all. Is this something known, that occured to others as well? Tried with multiple (Android) devices with different browsers, but the jumping always occurs ;). Could you take a quick look? I am not quite sure this is actually something caused by your plugin, but wouldn’t know anything else that could interfere.
All the best
Eno
Hello again :),
I just got a report back and can confirm, that with the next-to-last version (I never get any e-mails about updates, that is strange, have to pull them manually) input and select fields on any form, be it AJAX search, Gravity forms or hand-made forms, weren’t tappable on mobile at all. In rare cases you could press a bit longer on an input field and finally could enter something.
I just checked for an update and did a manual update to 4.8, and now other forms work well, only the search in the mobile menu still isn’t responding to touches. Do you have any idea if something from your side might be causing this?All the best
Eno
Hi Eno!
It’s nice to hear from you again 🙂
The form input issues were a known problem for compact layout, which I indeed fixed within the latest release.
I’m not sure however about the menu issue, it seems like it has connection to the plugin. I have tried to trace back and disable all event listeners via the console on mobile chrome dev tools, but it was still happening. The strange thing is, that on my iPad it was working fine.
I’m suspecting some kind of CSS and javascript event conflict, but I honestly have no idea why. Basically the focus is lost for some reason, even if I disable all the event listeners to the whole search field. However when I randomly put an input field into the menu via the source, and it was working fine. This means either that some event listeners are still not detached, or it’s something completely different.What happens if you turn off the compact layout mode? Is the problem still happening then?
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
Hi Ernest,
thank you for your thorough answer. I just had a peek at a similar thread and had already tried out the code you mentioned there, tailoring it to exactly only the search instance at hand, but didn’t have any luck with it. Also, turning off compact mode didn’t help, the field is accurately expanded, but no tapping possible. The fun is, when you try a random URL to trigger the 404 page when there is a second, almost identical search form, that form actually IS working.
All the best
Eno
You must be logged in to reply to this topic.