Go to App vs. Login?

I've noticed this. I don't believe that it's an issue with the module. Rather, it's facebook's new way of displaying the Oauth authentication page. Very misleading for users!

It's part of the reason that I'm attempting to display the authorization screen in a popup here:
http://drupal.org/node/1364698

The popup screen still uses the text 'login with facebook'

I'm getting some wild inconsistency from Facebook on this. My D6 site said "Go to App" but my D7 one said something like "Continue" (I'm not sure what the exact wording was. I think Facebook is A/B testing different dialogs.

That's interesting. I've been testing this frequently and I've yet to see the 'Continue' button. I wonder if this may be dependent on the scope of the oauth request, or perhaps some other parameter. Are all other conditions (apart from difference in major Drupal version) consistent?

Strange, I only saw the "Continue" button once today. Now I'm getting "Go to App" consistently every time. I tried to screenshot the results, but since I can't get the other version, here's the "Go to App" version for reference.

Yup. That's the screen that I've been getting each time.

I played with integrating the Facebook Javascript SDK with Fboauth to present a modal dialog, but it felt messy. I mentioned some of the work here: http://drupal.org/node/1364698

Looks like you're in the midst of a nice issue sprint for this module! Good work.

I played with integrating the Facebook Javascript SDK with Fboauth to present a modal dialog, but it felt messy. I mentioned some of the work here: http://drupal.org/node/1364698

Yeah I'm definitely not going to be using the Facebook SDK for this project. Including it with the project is a non-starter. Considering the license is Apache 2.0, we're not allowed to include its code on drupal.org even if we wanted to. But even if we could, my past experiences with the SDK indicate it is wildly complicated for the scope of functionality we're wanting in the FBOAuth module and I wouldn't use it anyway.

Might be of interest... this is a quote from a FB engineer at http://developers.facebook.com/blog/post/2012/03/02/enhanced-auth-dialog... (you have to scroll down for the comment to appear).

the four cases are context-sensitive and currently, there is no control for you to pick a particular button text. We show different button text in different situations, as we've found that users are more likely to install your application if the call-to-action text aligns with their expectations. Thus, the logic currently is something like*:

- if the user has already installed the app and you are requesting additional permissions that includes "publish_actions", we use "Add to Facebook"
- if you're a game app, we use "Play Game"
- if your auth dialog is shown in display=popup (e.g. after user clicks a "Log In with Facebook" fb:login button), we use "Log In with Facebook"
- in other situations, we use "Go to App"

*Obligatory Disclaimer: We may adjust the logic tree in the future without notice, as we're constantly testing variations to improve the user-auth experience. But hopefully this is helpful so you can at least understand how it is currently functioning under the hood :)

It looks like we can make the button say "Log in with Facebook" if we add &display=popup to our login URL. This issue might be resolved by implementing #1364698: Popup / modal dialog?.