> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/release-notes/release-notes-archive/release-1.7.37.md).

# Release 1.7.37

This release contains a regression, and will not be published

### ✨ Enhancements

* New Mod Launcher tab in the Sidebar
  * Can close and reopen tabs. Closed tabs remain closed on all tabs until reopened with the Mod Launcher. (#[6161](https://github.com/pixiebrix/pixiebrix-extension/pull/6280))
  * Sidebar forms can be closed by clicking the `x` button in the tab. Removed the `Cancel` button from all sidebar forms. (#[6167](https://github.com/pixiebrix/pixiebrix-extension/pull/6281))
  * Make Mod Activation Panel closable (#[6271](https://github.com/pixiebrix/pixiebrix-extension/pull/6287))
* Automatic refresh token support for MS Azure and other integrations (#[6284](https://github.com/pixiebrix/pixiebrix-extension/pull/6291))
* Page Editor Improvements
  * Clicking on a Document Renderer Header Node in the Brick Actions Panel focuses the related Document Builder Preview Element in the Data Panel (#[6211](https://github.com/pixiebrix/pixiebrix-extension/pull/6249))
  * Clicking on a Document Builder Preview Element in the Data Panel scrolls the Brick Actions Panel to the relevant Header Node (#[6228](https://github.com/pixiebrix/pixiebrix-extension/pull/6273))
  * Clicking on a child node in the Brick Actions Panel updates the styling to make it more clear which node has been focused (#[6229](https://github.com/pixiebrix/pixiebrix-extension/pull/6292))
  * Moved margin and padding drop-downs to the new `Advanced: Layout` section of the Brick Configuration Panel (#[6093](https://github.com/pixiebrix/pixiebrix-extension/pull/6256))
* Updated marked dependency to latest — markdown renderer no longer adds ids to heading tags, and the `mailto` in email links is no longer mangled. Email links in markdown will now open the user’s default mail client (#[6264](https://github.com/pixiebrix/pixiebrix-extension/pull/6264))

### 🐛 Bug Fixes

* Removed unnecessary scrollbar from sidebar when rendering large iframes (#[6289](https://github.com/pixiebrix/pixiebrix-extension/pull/6289))
* Clearing a property in the `Extract from Page` brick no longer throws an error (#[6275](https://github.com/pixiebrix/pixiebrix-extension/pull/6312))

### 🧱 New/Updated Bricks

* `Map/Transform Values`: synchronously or asynchronously map values
* `Split/Chunk Text`: split text into overlapping chunks
* `Convert Document`: convert between HTML/Markdown/Text
* `Search Text`: search for all occurrences of a word/phrase in text. Supports stemming
* `Highlight Text`: add support for case-insensitive matches and matching across HTML elements
* `Emit a Custom Event`: replaced eventName textbox with a creatable dropdown. Users can select an existing custom event or create a new one (#[6286](https://github.com/pixiebrix/pixiebrix-extension/pull/6288))


---

# 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.pixiebrix.com/release-notes/release-notes-archive/release-1.7.37.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.