> 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/jp/browser-extensions/browser-extension/older/browser-extension-version-12.5.0.md).

# Browser Extension Version 12.5.0

Released on August 6, 2019

This is a bug fix release to address several site-specific Autofill issues. Chrome, Firefox and Edge browsers have been released. Safari will release with the next Desktop application update.

* KeeperFill was removing some form elements of certain sites. The reason this was happening is because certain websites liked to inject an "eyeball" element to allow users to see the password that they were typing in. We attempted to control this by removing the feature of the target website, but unfortunately it caused issues with certain sites. This has been reverted and we have addressed the issue.
* Resolved performance issues that affected the BlackBoard university systems.
* Improved Fill issues on dozens of reported websites
* Created Backend support for upcoming TOTP field types release


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.