I don't think it's a huge problem at this time. However, if there is a substantial increase in the number of folks using Incognito (especially on mobile devices) it could become more than a quirk one can live with.
I suspect the double call is because login is handled asynchronously. The page's (session?) state isn't being refreshed on return, so it doesn't realize the session is now authenticated. Easiest might be to move the static parts to an updatable region that can be refreshed on demand, and call the refresh before exiting the login handler.
|