No FB Login with Internet Explorer 10

Enough,
It's Facebook Javascript issue, so not something we'll be able to fix in JFBConnect. What will need to be done is a submission of a bug report to Facebook. I've created the text of the submission before that you can simply cut and paste into a new bug report. Alternatively, you can go to your Facebook application and add us as an administrator of your app so we can submit the report on your behalf. The report needs to include the App ID of a failing app, which we don't have any (this site works in IE10).

My Facebook email address is This email address is being protected from spambots. You need JavaScript enabled to view it.

To submit the bug report yourself, go to:
developers.facebook.com/bugs/create
Title: onlogin event not triggered in IE10
Description: The onlogin event of the fb:login-button is not being triggered in IE10. It works in all other browsers.

A similar issue was marked as resolved in December, but we're still seeing the issue. Additionally, there are user comments in the attached bug report stating that the issue still exists for them as well. So, I'm re-submitting this as a new bug to make sure it gets visibility:
developers.facebook.com/bugs/436663883038917

Tags: User Login, Login Button
Apps: <Your App>
Steps to Repro:
1) While using IE 10 (use privacy mode to be sure you have a fresh set of cookies), go to: [/b]<Your Website's login URL>[/b]
2) While not logged in, press the "Connect with Facebook" button.
3) When the dialog pops up, enter your credentials and approve the app.
4) Dialog box goes away, but no callback is invoked so the page does not refresh or redirect in any way. (nothing happens)

Expected Behavior:
The onlogin event is triggered, which calls our Javascript to log the user into our system. This happens correctly in all browsers except IE10.

Actual Behavior:
Nothing. No call back is triggered in IE10 only.

As for your subscription expiration, if it turns out there is a change that's required to JFBConnect to fix this issue, we'll gladly provide it to you whether your subscription is active or not.

Hope that helps,
Alex

I'm not sure if the above bug report was ever submitted by a user. Unfortunately, you can't really submit a bug to Facebook if you aren't an admin of an application that is experiencing the problem.

I'd highly, highly, highly recommend following the steps above to re-submit a new bug report to Facebook stating that the issue still exists. The old bug report is closed, which means comments aren't being looked at and this issue likely won't get attention for the few users that are having the problem *unless* a new bug report is submitted to make them aware the issue still exists.

Hope that helps get you started. If you submit the bug report, please link to it here so we can provide it to others if they have the problem and help push it higher for Facebook to prioritize more.

Thanks,
Alex