Bug: If user has a browser window with the log opened by clicking the "log" button, other http connections are denied

[jonpanozzo]

There are actually a few pages that work like this where the system becomes bound to the browser of the device with that window left open. I also would wager this is potentially where many of the claimed "webGui is unresponsive" errors are coming from (people leaving windows open with the log or something and then not being able to get back in).

To recreate:

1. Open browser to webGui on device A and click "log" in the top right.
2. Open browser to webGui on device B and it hangs.
3. Close log pop-in on webGui on device A and webGui becomes available on device B and A.

We should build a list of all the webGui functions that call a pop-in and bind the http session to that single device and really rethink whether that makes sense or not. When doing a "check for updates," I think it makes sense (to prevent others from manipulating data while operations are in affect). But for a log, I don't think that's a good idea.