> 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-march-2023.md).

# Improvements and fixes, March 2023

Improvements and bug fixes released in March 2023.

*31 March 2023*

## Improved

* **Portal:** "All Guides" table export now includes Guide names and corresponding Guide IDs.
* **Portal:** UI improvements of loading and empty states, number formatting, and illustrations.
* **Portal:** Uniform UI hero boxes and buttons across the Portal.
* **Portal:** Analytics wording simplified (calculations unchanged). CSV export now includes totals.
* **Editor:** Updated design of toggles and dropdowns. Autofill speed adjusts based on text length.
* **Editor:** New Guide step design for faster end-user interaction with the underlying application.
* **Editor:** Dark color update and new slide toggle sizes. "View Analytics" button added in Tags List view.
* **Editor:** Tooltips with icons can now be used inside iFrames. Tooltip content can be targeted with Page Segmentation.
* **Other:** Recording elements inside iFrames located inside shadow roots now supported. Updated Code Selector Engine for Shadow DOMs.

## Fixed

* **Portal:** Language codes now displayed correctly in the activation choice. "Users" metric now matches on Retention and Engagement pages. NPS analytics visible without HEART enabled.
* **Editor:** Prevented a created Tooltip from overriding another Tooltip name. Tooltips now display in Preview mode. Error shown for duplicate Tag names.
* **Other:** Screenshots of reselected elements and elements on different pages now shown correctly in exported PDFs.


---

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