> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/changelog/2023-and-older/2023/improvements-and-fixes-july-2023.md).

# Improvements and fixes, July 2023

Improvements and bug fixes released in July 2023.

*31 July 2023*

## Improved

* **Portal:** Smaller UI improvements (padding adjustments in HEART Analytics pages, button updates).
* **Portal:** Date picker now uses "Current month", "Previous month", "Last 3 months" with auto-calculation. Added "Yesterday" and "Last 7 days" options.
* **Editor:** Improved Editor support on smaller screens. Updated Tags overview page for empty state.
* **Editor:** Additional improvements for appendToTarget to support more complex scenarios.
* **Editor:** Removed dark background and element highlight when Managers pause recording. Help docs icon linked to individual content pages.

## Fixed

* **Portal:** Password managers now work with the Portal login form. Fixed Announcement wordings.
* **Editor:** Cross-Origin iFrame content can now be visualized and interacted with by end users. Fixed Hint icon repositioning, segment list display, long word wrapping in Tooltip text boxes, Preview from skip step, and numerous other Editor UI fixes.


---

# 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.userlane.com/changelog/2023-and-older/2023/improvements-and-fixes-july-2023.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.