# Browser Extension Version 16.4.14

### Bug Fixes <a href="#bug-fixes" id="bug-fixes"></a>

* **BE-4923**: Protection against Chromium crash when max IndexedDB reaches quota
* **BE-4928**: SSO Logout generating duplicate requests to the server, creating replay error
* **BE-4952**: Browser Extension crashes when switching VPN connections while logged in
* **BE-4953**: Record matching stops working properly after network changes occur on the user's machine
* **BE-4960**: When a user has Firefox set to "never to remember history" in the security settings and disconnects from the network, none of the records show for a specific domain after reconnecting.
* **BE-4942**: When a user deletes a record from a domain then logs out and logs in again, the other records on that domain disappear when navigating to that domain.
* **BE-4943**: The browser action window crashes on startup sometimes because the tabs value is undefined or null from a chrome listener. This makes it so that initialization steps in the extension don't complete because these thrown errors interrupt the startup process.

### Improvements <a href="#improvements" id="improvements"></a>

* **BE-4682**: Extension reverts to Backup 2FA over WebAuthn with Cloud SSO activated account With this update, SSO Cloud accounts that enforce 2FA will default to the use of WebAuthn instead of TOTP/SMS.
* **BE-4934**: In order to reduce sync calls in large enterprise customers with many shared records, the browser extension will process closely received incoming messages in batches.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.keeper.io/release-notes/jp/browser/browser-extension/older/browser-extension-version-16.4.14.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.