# Browser Extension Version 15.3.5

## Bug Fixes and Improvements

* BE-4000: The password generator only allows a maximum of 51 characters (should be 100)
* BE-4008: IP Addresses are displayed and linking incorrectly in record view of search results
* BE-3916: SSO login to extension generates "update your account settings" error
* BE-3742: "Prompt to Update" dialogue disappears too quickly on page redirect
* BE-3707: Payment card autofill fails on portal.azure.com
* BE-4013: Creating a record at walmart.com registration screen submits the form prematurely
* BE-4036, BE-4016, BE-4017, BE-4019, BE-4021: Fill button fails to fill existing record on various sites
* BE-4020, BE-4022: Auto Submit fails on various sites
* BE-4025: Auto Submit occurs on various registration forms when it shouldn't
* BE-4026: The second password fields of various registration forms are not filled when a new record is created
* BE-4015: Privacy Screen allowed user to copy password in one particular flow
* BE-3998: If user explicitly turned Autofill OFF, don't prompt to turn autofill on anymore.
* BE-4002: Improved Password Change detection routine to ensure password is saved even if the user forgets to click Save.
* BE-4035: Records are not deleted for the user immediately when the user is removed from a Team.
* BE-2358: Fixed auto-submit on Lifelock website
* BE-3968: Locked down Content Security Policy embedded within the extension.
* BE-4012: Improved synchronization with the Web Vault and backend system for Logout persistence.

<br>


---

# 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-15.3.5.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.