Added custom JS and I’m no longer able to fill the Marketo forms in Android | Community
Skip to main content
New Participant
May 24, 2024
Solved

Added custom JS and I’m no longer able to fill the Marketo forms in Android

  • May 24, 2024
  • 1 reply
  • 1954 views

Hi team,

 

I am not able to type the textfield in Android phone by using Marketo form. And i have used the below code.

<script> $( window ).resize(function() { if ($(window).width() < 991) {$('#moveForm').appendTo('.form-resp-bot-element');} if ($(window).width() > 991) {$('#moveForm').appendTo('.form-resp-bot-element');} }); </script>

 

because of this it's causing the issue. If i removed this code it's working fine. Please help on this.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

Focusing a form input fires a resize event. You get caught in a loop where you’re moving the form over and over, each time losing focus.

 

You must check if the width has actually crossed over your breakpoint since the last resize. Don’t move the form if it’s already moved to the expected plance.

 

Also, the code currently on the page is throwing a fatal error, as you can see in the F12 Console (on both desktop and mobile).

1 reply

SanfordWhiteman
New Participant
May 24, 2024
It's simply not possible to help with this if we don't have a link to your page. Your code refers to elements that aren't even part of a Marketo form!
Arun-PAuthor
New Participant
May 25, 2024

Please find the test URL. Kindly check in Android device.

 

https://respond.apptio.com/01-Testing_Android_LP.html

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
May 25, 2024

Focusing a form input fires a resize event. You get caught in a loop where you’re moving the form over and over, each time losing focus.

 

You must check if the width has actually crossed over your breakpoint since the last resize. Don’t move the form if it’s already moved to the expected plance.

 

Also, the code currently on the page is throwing a fatal error, as you can see in the F12 Console (on both desktop and mobile).