Hi th55, Some of those pages (create new account, Gmail, etc.) have frame busting code to prevent iFrames. If you're worried about users clicking those links, I wouldn't iFrame the AuthSub flow. Note, most of the time users will already be logged in to Google so they'll never receive the Google Login page.
While iframing the AuthSub experience _will_ work, is there a reason you need to do so? Could you just fetch the token with normal browser redirects and use AJAX magic after the linking has alread been established? Eric On Nov 19, 4:40 am, th55 <[EMAIL PROTECTED]> wrote: > Our application uses an IFrame with screen tanned css background > (typical Ajax these days) to present the import/export functionality > to Google Health to our users. This includes the "Link to Google > Health" which does the authorization token work. On initial link , > the Google login page appears in the IFrame and is well behaved. The > login page and the 2nd profile authorization page appear in the IFrame > and both are well behaved. Now, in the past, if my memory serves me > correctly, clicking one of the many other links in that login page > still caused the resulting page to render within in the confines of > the IFrame and be well behaved. That is, if I clicked a link such as > "Gmail", "Web history" or "Create an account now", the rendering > appeared within the confines of the IFrame. However, when I tested > those other links again the other day, when I clicked "Create an > account now", the Google page took over the whole browser window and I > lost my application page entirely. It blew away my page, IFrame and > all. I dont' think it used to do that. Has something changed on the > Google side? Can Google make those other links stop taking over the > whole browser window on rendering? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Health Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/googlehealthdevelopers?hl=en -~----------~----~----~----~------~----~------~--~---
