Home/ Questions/Q 6933007
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T11:46:38+00:00

I’m calling FB.login() on a click event in my application. The dialog pops up

  • 0

I’m calling FB.login() on a click event in my application. The dialog pops up as expected, but when the user is done logging into Facebook (and/or authorizing the app), the dialog does not close. Instead it loads a white page (inside the dialog) and the title changes to XD Proxy.

This only happens on Google Chrome (I’m using the latest version available right now for Windows 7).

This doesn’t happen if Chrome is in Incognito mode.

The fb-login ‘social plugin’ works fine on Chrome.

To test/debug this further, I created a new Facebook App with vanilla settings. The only change I made was set the Site URL in the app settings. Here’s HTML code that you can use to recreate this bug.

Sample Code for recreating issue

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
    <head>
        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
        <title>Chrome Bug Test</title>
    </head>
    <body>
        <button onclick="dologin()">Login using Facebook</button>

        <div id="fb-root"></div>
        <script src="http://connect.facebook.net/en_US/all.js"></script>
        <script>
          FB.init({
            appId  : '[YOUR APP ID HERE]',
            status : true, // check login status
            cookie : true, // enable cookies to allow the server to access the session
            xfbml  : true  // parse XFBML
          });
        </script>

        <script type="text/javascript">
            function dologin(){
                FB.login(function(r){
                    if(console && console.log) {
                        console.log(r);
                    }
                });
            }
        </script>

    </body>
</html>

Facebook Settings that I’ve tried changing

  1. Setting a site domain, didn’t change anything.
  2. Using a custom channelUrl and channel file, didn’t help either.

Related bugs tracked at Facebook

Related issues here on Stack Overflow

I’ve seen many people come across this, but what bugs me is that I haven’t been able to find a concrete fix for this. Facebook hasn’t responded to bug reports yet. One solution would be get rid of Javascript based authentication code and do it solely using serverside mechanism (Facebook PHP SDK). I’d like to avoid that due to time constraints.

Anyone have any ideas how to fix this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Calling this snippet after FB.init fixed the issue for me. But other solutions seem to have worked for different cases.

    $.browser.chrome = /chrome/.test(navigator.userAgent.toLowerCase());
if ($.browser.chrome || $.browser.msie) {
    FB.XD._origin = window.location.protocol + "//" + document.domain + "/" + FB.guid();
    FB.XD.Flash.init();
    FB.XD._transport = "flash";
  } else if ($.browser.opera) {
    FB.XD._transport = "fragment";
    FB.XD.Fragment._channelUrl = window.location.protocol + "//" + window.location.host + "/";
  }
    • 0