> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/browser-extensions/browser-extension/browser-extension-version-16.4.7.md).

# Browser Extension Version 16.4.7

## Features & Improvements

* **BE-4595**: Updated to the latest Keeper Javascript SDK
* **BE-4534**, **BE-4010**, **BE-4535**: Migration to MV3

## Bug Fixes

* **BE-4479**: 2 single tab windows with different domains confuses the context menu
* **BE-4623**: Extension does not allow users to retry with different Enterprise Domains
* **BE-4494**: After moving a subfolder out of a folder, the extension shows info in 2 locations
* **BE-4593**: User not taken to Web Vault when clicking vault button from sign-in screen
* **BE-4587**: Mouse changes from arrow to hand on record title
* **BE-4639**: Editing the URL from the extension does not reflect in the UI
* **BE-4659**: Users in AU are not auto-logged-in to the extension when installing it from within the Vault.
* **BE-4646**: Error message "object already exists" when logging into the GovCloud region.
* **BE-4661**: MAPFRE website causes JS error
* **BE-4692**: Open in Vault does not open the record when the vault is already open in another tab.
* **BE-4695**: KeeperFill is showing in Gmail search box
* **BE-4703**: Prompt to Save is not showing correctly when the user does not have a record in their vault.
* **BE-4701**: Expiring the Master Password does not show the proper error message in the UI.
* **BE-4716**: Filling on VMware Horizon with Autosubmit does not click the correct button.
* **BE-4717**: Throttling message not being displayed in the UI properly in some cases.
* **BE-4691**: Vault Transfer consent notice not showing in the browser extension


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/release-notes/browser-extensions/browser-extension/browser-extension-version-16.4.7.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.