Comment 4 for bug 1421715

Revision history for this message
Olivier Tilloy (osomon) wrote :

Opening a new popup window for the sign-in process really is a broken workflow… Anyway as Riccardo mentioned, once we have an animation in place to inform the user that a new background tab was open, this will be less of an issue.

I tried logging in to feedly using my google account, and the login appeared to be successful. the newly open tab said that it should automatically close itself, but it didn’t (known issue being addressed, see bug #1353453).

Tried running it with https://code.launchpad.net/~osomon/webbrowser-app/on-close-requested/+merge/240437, and the tab didn’t close either, I’m seeing the following errors in the console:

    [JS] (http://feedly.com/feedly.html?code=ApNPWjd7ImkiOiJkYzU2NmVmZC1lZDY2LTRmZDctOWQ0OS1lYzdiZTg5NDRkY2EiLCJ1IjoiMTA3NDYzMDc2ODA5NTQ2MTgyNTg2IiwiYSI6ImZlZWRseSIsInAiOjYsInQiOjE0MjQwODcwMzY5NDB9&state=:61) [feedly] callback to opener failed:SecurityError -- Blocked a frame with origin "http://feedly.com" from accessing a cross-origin frame.
    [JS] (http://feedly.com/feedly.html?code=ApNPWjd7ImkiOiJkYzU2NmVmZC1lZDY2LTRmZDctOWQ0OS1lYzdiZTg5NDRkY2EiLCJ1IjoiMTA3NDYzMDc2ODA5NTQ2MTgyNTg2IiwiYSI6ImZlZWRseSIsInAiOjYsInQiOjE0MjQwODcwMzY5NDB9&state=:63) Uncaught TypeError: Cannot read property 'slice' of undefined

If I close the tab manually and refresh the initial tab, I’m not logged in, so something is not working properly indeed.