homebrew update leaves chrome in unstable state

[twistedmelonman]

When homebrew update does an update of the Google Chrome cask while Chrome is running, the running Chrome instance loses network resolution -- web requests time out or fail with a X icon. This is immediately resolved by quitting and restarting Chrome.

Ideal solution: homebrew update of Chrome does not break running Chrome.
Acceptable solutions:

1. exclude Chrome from homebrew update; it has its own reasonably robust self-updater
2. some kind of detached-process mechanism, where if homebrew detects there is a Chrome cask update, it spins off a separate process that doesn't block the main homebrew-update. the separate process would have a UI guard; an affirmative "there's a chrome update, do you want to quit now" and only proceed if yes.

(1) is obviously a lot easier.