Address the renegade Chrome loading spinner issue

[GoogleCodeExporter]

There is currently a race condition where if the Google auth code hasn't 
finished running before we send out a long-standing GET to the state server, 
that the loading spinner goes on for 20 seconds.

Fortunately this is all cosmetic, as the page still loads just as fast and you 
can interact with it just fine.

Dan's theory is that Chrome's heuristic is that at long as there are some 
outstanding requests, the thing keeps spinning.  When the auth stuff finishes 
before the long stateserver request, there is a gap that Chrome can identify as 
the page being loaded.  If that long request goes off before we come back for 
auth stuff, there is no gap.

Any fix is likely going to need to create such a gap, either by guaranteeing a 
sequence of actions, or by adding a time gap explicitly.

Original issue reported on code.google.com by rich.br...@gmail.com on 18 Jan 2013 at 4:13

[GoogleCodeExporter]

This doesn't really cause any real issues, so bumping the priority down.

Original comment by rich.br...@gmail.com on 24 Jan 2013 at 10:22

• Added labels: Priority-Low
• Removed labels: Priority-Medium