# Browser Extension Version 17.5.0
## Summary
The Browser Extension version 17.5.0 is primarily a stabilization release with an assortment of bug fixes.
## New Features
* **BE-6994:** Added new role enforcement policy to manage access to the Snapshot Tool
## Bug Fixes
* **BE-6415:** Clean up the Lock Fill CS Redux state
* **BE-6495:** Clean up the feature flag `MP_REENTRY_MODAL_IN_TOOLBAR_WINDOW`
* **BE-6520:** Clean up Record Item component
* **BE-5296:** Change Password is Not re-rolling Password to Policy on Revealed Passwords
* **BE-6302:** Autofill unintentionally populating the "email" attribute in the SSO configuration when a matching record is detected
* **BE-6324:** Form Fill - Privacy screen is incorrectly showing for record owner
* **BE-6408:** Right side padding on RTL languages is too narrow or non-existent
* **BE-6466:** Remove static emails from binary
* **BE-6469:** Custom record not appearing in toolbar window
* **BE-6503:** Prompt to save did not come up for many sites, including espn.com, netapp.com ..
* **BE-6538:** Prompt to save: apple.com (continuation of BE-6503)
* **BE-6539:** Make sure the passkey prompts look good on the GitHub site when user's system setting is dark mode
* **BE-6542:** Entering a nonsense secret code for 2fa scanner leads to UI corruption
* **BE-6554:** Password generated by change password flow has no lowercase letters
* **BE-6573:** "Prompt to Save" fails to appear for enterprise user if they have a Password Generator enforcement. (password complexity prompt)
* **BE-6574:** Missing warning prompt when turning on Stay Logged In
* **BE-6592:** BG script pulled in into extension options page
* **BE-6640:** PAM record changes cause BE to crash
* **BE-6673:** Design mismatch: RESTRICT\_TOTP error dialog
* **BE-6680:** Hover icons appear though its not hovered in the toolbar window
* **BE-6719:** Toolbar window is completely blank (white) when resuming from sleep/standby mode.
* **BE-6753:** Users can add 2FA codes to record without re-authentication in the browser extension
* **BE-6857:** Search Bar - text not clearing
* **BE-6864:** Focus is not on the search bar when user clicks on the toolbar icon.
* **BE-6980:** HubSpot - page title incorrectly recognized as a login field for autofill (be-autofill-ignore) (part 1 of 2 short term fix)
* **BE-6986:** Dark mode - white square in landscape mode
* **BE-7000:** Favorite icon tooltip cut off
* **BE-7004:** Extension tab - "Save" button appears in white when in dark mode.
* **BE-7006:** Record list filters include suggested records when search is "active"
* **BE-7007:** Favorite button. Hovering over a record containing TOTP
* **BE-7009:** Tooltip needed on favorites icon
* **BE-7010:** White screen appears after user clears search bar.
* **BE-7011:** Security key user unable to progress through device approval flow
* **BE-7012:** Record hover, click and drag highlights container & 'ghost text' (white-on-white) hard to read for dark mode
* **BE-7013:** Prompt-to-save disappears when logging into a new website for which you have creds but no vault record yet
* **BE-7014:** Typo 'Recents' should be 'Recent' (singular) for search filter
* **BE-7015:** Mac Chrome - Browser Extension initial focus on login on top left 'three dots' rather than next button
* **BE-7024:** Unable to click Account Transfer popup on login
* **BE-7025:** Search in Browser Extension "glitchy" when typing/deleting
* **BE-7035:** Admin password complexity domain-specific rules not enforced on Prompt to Save
* **BE-7073:** BE installed with Web Vault on same browser instance causes spinner when special parameter is appended to URL of web vault instance
---
# 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/browser-extensions/browser-extension/browser-extension-version-17.5.0.md?ask=
```
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.