ATTN: Hotfix for broken embedded forms in Firefox 46 (release date April 19) | Community
Skip to main content
SanfordWhiteman
Level 10
February 27, 2016
Question

ATTN: Hotfix for broken embedded forms in Firefox 46 (release date April 19)

  • February 27, 2016
  • 11 replies
  • 5760 views

Warning! On the near horizon is a version of Firefox that will break embedded forms.  As I noted in Firefox Developer Edition​, Firefox 46 -- already in-the-wild for folks using Firefox Developer Edition -- is moving into Beta on March 8 and will be released worldwide via auto-update on April 19.

Luckily, your faithful forms guy has a fix you can put in place now to avoid disruption.  Add the following style either in a <style> tag or via an external stylesheet.  If you use an external stylesheet, make sure it loads before forms2.js/forms2.min.js.

#MktoForms2XDIframe {

    visibility: hidden;

    position: absolute;

    display: block !important;

}

  • The breakage affects forms using the embed code. It does not affect native form objects on Marketo-hosted LPs, but it can affect forms loaded as embeds (in HTML blocks) on Marketo-hosted pages. If you are not sure which method you use, apply the fix.
  • Marketo Support has been made aware of the issue but has not planned an official fix.
  • The change is related to Gecko's reinterpretation of the CSSOM getComputedStyle method. It should be noted that Chrome and IE are not planning to use the same interpretation.
  • If you want more details you can DM me.

11 replies

Dan_Stevens_
Level 10
February 27, 2016

Thanks, Sandy - this is super helpful.  Has Marketo tried to hire you yet!?

SanfordWhiteman
Level 10
February 27, 2016

Maybe the offer got caught as spam.

SanfordWhiteman
Level 10
February 27, 2016

Also CentralChampionsNYC MUG​ because I could only put this in one Place.

And blogged about here.

Grégoire_Miche2
Level 10
February 28, 2016

Thx Sanford !

February 29, 2016

Awesome, thank you for the post!

Kenny_Elkington
Adobe Employee
Adobe Employee
February 29, 2016

Thanks for reporting this.  I'm having engineering take a look right now.

SanfordWhiteman
Level 10
February 29, 2016

Thanks, Kenny. My blog post (linked above) has more.

Kenny_Elkington
Adobe Employee
Adobe Employee
March 8, 2016

We have a patch prepared for this which should be going live in the next few days.

Kenny_Elkington
Adobe Employee
Adobe Employee
March 9, 2016

This is live now.

April 29, 2016

Has anybody encountered issues with this hotfix in some scenarios? We have Drupal sites where this fix worked fine - but there's a Wordpress 4.3 site where things don't seem to be taking. The code was added to the CSS and loading above the .js on the page. Browser and Server side caches cleared, but still the form won't show.

SanfordWhiteman
Level 10
April 29, 2016

You shouldn't need my hotfix anymore as the core lib has been patched.

You can send me a link to your page and I'll check it out, but please remove the "userland" hotfix first.

April 29, 2016

I wondered about that, per a note a couple above, here. But, unfortunately, it seems I did. I had to on our main site, and it worked.

Unfortunately, the Wordpress site is handled by somebody else, and I'm still waiting to hear back from them. Here's the link, in any case: Newsletter Sign-up - Third Certainty

This leads me to ask, is there a setting or something I need to change in Marketo or elsewhere, for the official fix to take?

SanfordWhiteman
Level 10
April 29, 2016

This leads me to ask, is there a setting or something I need to change in Marketo or elsewhere, for the official fix to take?

Nope, and Third Certainty has the latest.

Give me a few minutes and I'll find the problem.

April 29, 2016

That looks right. Strange. I'm on Firefox 46.0, on Mac 10.11.13... also, viewing in privacy mode.

...oh.. it works, if I'm not in privacy mode! Ok...Is there something about privacy mode that makes the form go away? Maybe the Munchkin code/cookies

SanfordWhiteman
Level 10
April 29, 2016

It's not Munchkin. It's that forms2.js is on the tracking protection list because it's on a Marketo domain.

     "The resource at "app-ab14.marketo.com/js/forms2/js/forms2.min.js" was blocked because tracking protection is enabled."

This is a known thing.

April 29, 2016

Ahhh.. got it! Ok. Thank you!

Grégoire_Miche2
Level 10
April 29, 2016

And vote here:

-Greg