We'd like to perform the OAuth login in an IFRAME, but Twitter
redirects the window.top to the page if it detects that it's IFRAME'd.
Is there a reason why we *must* show a window.open()?
The reason why this is an issue is because the window.open() approach
is not modal, i.e. we cannot force the
hi.
i think this is one of the general frustrations with oauth - the whole idea
is that the customer would see that the URL bar has a secure
twitter.comURL. i'm not sure how you would demonstrate that if in an
iframe.
On Tue, Dec 22, 2009 at 12:48 PM, jxdavis jxda...@godaddy.com wrote:
We'd
Have a look at how Facebook handles it.
When they do a window.open() there is a notification in the existing window
directing the user to look for the new window. When the new window closes
the notification automatically goes away.
Look under Linked Accounts:
