I’m afraid you do. That setting only works if an extension asks for it. If no extensions ask to keep running, Chrome shuts down even if the setting is enabled.
Ahhh, good to know.
It looks like the function is designed to differentiate between these two scenarios:
-
set bitwarden to lock on browser restart, keep browser open > press ‘Win logo + L’ to lock PC > log back in ====> bitwarden stays unlocked.
-
set bitwarden to lock on on PC lock, keep browser open > press ‘Win logo + L’ to lock PC > log back in ====> bitwarden is locked.
If browser closes bitwarden locks in all cases.
Yeah exactly. And in both cases Bitwarden behaves wrong
If this is expected behaviour I also think this is misleading in the majority of use cases.
I’m on MacOS and the extension locks whenever I close the Google Chrome window, despite the application still being open in the background, the extension locks.
I don’t really want to download another extension and I’d rather some solution that isn’t too resource-heavy (though this may be asking too much).
I can’t find a setting for “Keep Chrome running in the background” and it seems to do that anyways - why does Bitwarden then lock?
If there’s no good fix, I’ll use a PIN.