Trying to pull in a Marketo form through an iFrame. We've noticed Chrome will randomly reject the iFrame and not load the form. We can't consistently recreate the bug, but I'd say it happens 50% of the time.
Anyone ever experienced this?
As far as I can see, this is a Chrome 69 bug only, not existing in versions on either side of 69. Not the first time (by any means) such a thing has happened!
Chrome 70 is going to go Stable around October 16th. This means 3 more weeks of dealing with your forms not rendering, or switching to embeds. As far as I can see the problem persists even when the IFRAMEs are the only elements in the page, so there's nothing else to trim down or tweak. It happens a lot less than 50% of the time for me, though. More like 5%.
You'll have to provide a URL. Surely the root cause is not going to be truly random, unless you're actually generating a random number in code! More likely, you have a race condition which creates different results based on network conditions. Fixing that race will be the goal. But we need to be able to see what you're seeing first.
When it "rejects" the IFRAME, what is the console error message?
That's what's so strange - there's no console error message. We just see a red "200" that indicate the IFRAME didn't load.
Let me see if I can repro it. What version of Chrome/Mac, and are you opening and closing Incognito to trigger the issue, or can you trigger it within the same browser session?
I'm on Chrome 69 and macOS High Sierra 10.13.6.
I can replicate the issue multiple times in a single session in both Incognito and regular browsing.
I can repro in Chrome 69, but not in Chrome 68 (as yet). Will check in current Canary. If it's not triggerable there, then there's a pretty clear conclusion.
Will have to resume later tonight as I have to go out for a bit.
Thanks for your help, Sanford. I really appreciate you looking into this.
Please let me know what you find / what the solution could be.
Thanks so much for your help! I really appreciate you diving into this. Seems like the issue is edge case and will be resolved shortly.
Also, while this itself will not cause the IFRAME not to render, I immediately see that the IFRAME and the main document don't share a private domain suffix. You should know that Safari will not send cookies to the inner document in this case, so (for example) Pre-Fill will not work. You've done a great job visually integrating these other documents w/the forms into your layout, but what's the reason you aren't using embedded forms?
Fair point. There were a variety of business-related decisions that set us down the path of IFRAME rather than embed... But if we can't figure out how to load the forms consistently through IFRAME, we may have to course-correct. Though I certainly hope that's not that case!
Also, the domain listed is just a staging link. The launch domain is millerheimangroup.com. Not sure if that matters.
Retrieving data ...