Doug Antkowiak // Mar 10 2011
Note: The following post was written on March 10, 2011. Facebook has since fixed Bug 15200 and pushed back the deadline for creating new FBML apps to Friday, March 18th as announced on the Facebook Developer Blog.
Having trouble viewing a Facebook iframe via https? You’re not alone.
When the Portent development team was hard at work upgrading our client’s Facebook pages from FBML to iframes, we discovered not everyone in the office could see the fresh content.
It’s officially listed as Bug 15200 and it affects any Facebook user who upgraded the privacy account settings in their profile to "Secure Browsing." Using Facebook with a HTTP Secure (https) connection allows you to maintain encrypted communication on the web and it makes it more difficult for someone to retrieve your data on the same network.
The Facebook iframe bug throws two wrenches into the social media marketing engine. First of all, it prevents an entire Facebook audience (one which is savvy enough to turn on secure browsing) from viewing your content: A major internet marketing sin.
Second, it holds a cloud of doubt over the March 11th Facebook page update. While FBML will still be functional for a limited time, Facebook marketers will no longer have the ability to upload FBML after this Friday — forcing any development of new content in iframes. Yeah, those same iframes that aren’t supported by HTTPS.
The worst part about this iframe update is that there’s no way for a Facebook user to know their personal user settings prevented them from viewing your brand-spankin’ new Facebook iframe.
Instead, they’ll just stare mindlessly at a white background, only to eventually bounce and never visit your brand’s page again because, to them, it "didn’t work."
All we can hope is that Facebook fixes the bug by Friday. Until then, please submit any ideas if you know a solution to the problem.