I don’t think it’s a new bug in this Canary, but a new bug in 2.1. To continue with an old question:
2.0.8.1 handles this more predictably and nicely. If you log out of a tab, it pops up a box informing
Trying to do things (seems very broad) in another tab gets the same thing. OK gets login screen.
One questionable behavior is after doing login, the OK to above box in another tab runs similarly despite access being open if you edit page URL to not have the login.html component any more. Consistency is often good, but convenience (just let tab in if user did login elsewhere) is nice too.
Now let’s try in 2.1.0.107. I think the 2.1.0.2 behavior is similar, although not completely identical.
Open two tabs to home page, refresh to remove the cached leftovers, Log out on one of the tabs. get a login.html screen. Go to the other tab and try to do something, e.g. click About, which goes “Loading” forever (with a message to TrayIcon console that most probably didn’t set up to check).
A job Run is ignored, and a job Edit gets
OK does nothing visible. Having learned that refresh often helps the flaky GUI, try that and get
and the Log in button at least leads to the login.html screen and access again, but it’s kind of ugly.
Ignoring things that seem like more clearcut bugs (like buttons that do nothing), what are planned interactions between Log out on a tab, and behavior on another tab in same or different browser?