Cc: ***@chromium.org ***@chromium.org ***@chromium.org
Comment #29 on issue 59285 by ***@chromium.org: Facebook connect login
popup does not close by itself
Comment 26 could be important-- is this bug ever observed when the original
page (e.g., mmaprofighter.com, millionairecity.com) is not installed as an
app from the Chrome Web Store? Even in version 9?
There's an explanation if it only happens for apps. The popup window will
switch to a different renderer process when going to a URL outside the
app's manifest, such as Facebook Connect. After a successful login, the
window navigates back to the original app and rejoins the original
process. (You can verify this by looking at the Chrome Task Manager to see
if the page shares a process with the original window or not.)
However, there's a bug in that window.opener is not valid when the
post-login page rejoins the original process. This prevents the page from
telling its parent window that the login succeeded.
Does anyone see this bug if the original page is not installed as an app
from the Chrome Web Store? If so, there's a different problem involved,
because we won't swap processes in that case.
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs