> 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/safari-extension/safari-extension-release-15.0.12.md).

# Safari Extension Release 15.0.12

## Improvements

* SE-443: Custom field values that contain URLs are now hyperlinked

## Bug Fixes

* SE-414: Various fixes for Web Vault and Safari Extension interactions and "Stay Logged In" setting
* SE-427: Request Time Out screen fails to appear once Keeper Push notification is left unanswered after one minute
* SE- 440: A JavaScript error is generated when the user attempts to open the Desktop App from the Safari Extension
* SE-445: Safari Extension fails to load a record after being shared
* SE-446: The SMS field of a record is autofilled with the username when SMS 2FA is enabled (PayPal and Amazon)
* SE-439: Logout timer fails after logging out and back in on Safari Extension
* SE-447: Users do not receive a notification when their Admin has disabled the "Stay Logged In" feature


---

# 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/jp/browser/safari-extension/safari-extension-release-15.0.12.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.