Error when a logged in tab attempts an action after another tab logs the user out

[Markus Korn]

If a user is not logged in and clicks in the 'Assigned to' field of a task, the AJAX widget pops-up and let the user search for an assignee,
 * selecting a user there results in an error """ Unauthorized (, 'transitionToAssignee', 'launchpad.Edit') """
 * selecting 'Assign me' closes the popup but let the progress throbber spin forever

Trying to assign a person to a task when not logged in should have the same behavior than the 'Status' field, it should just redirect to login.

Steps to reproduce:
1. Logged in open https://bugs.qastaging.launchpad.net/launchpad/+bug/2112
2. Open another tab and log out from there
3. Go back to the page opened in step 1
4. Click any of the edit buttons

You see the "Unauthorized (, 'transitionToAssignee', 'launchpad.Edit')" error rather than the login page.

[Robert Collins (lifeless)]

I suspect we want an in-place login widget or some such.

[j.c.sackett (jcsackett)]

This is already fixed; if you're not logged in you don't have an edit option for the "Assigned to" section.

[Robert Collins (lifeless)]

I've reopened this, because the internet is concurrent :) Easy way to reproduce:
 - login
 - open a bug page
 - log out without closing that page
 - perform the action

Now, we can argue that this is rare and shouldn't be high - sure.

OTOH if we zap our session database for some reason, *every* active user will suddenly run into this.

[Benji York (benji)]

This must have been fixed as a side-effect of some other change. If I perform the set of steps shown in the screen cast I don't get the never-ending spinner any more, now I get the expected error message box.

[Robert Collins (lifeless)]

reproduces easily for me following the description instructions