> 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-2.2.3.md).

# Release 2.2.3

Published to the Chrome Web Store on January 13, 2025

### 🎨 User Experience

* Custom Form Fields now have an optional toggle to autofocus the field on initial render

### :bug: Bug Fixes

* Fix Action Menu Positioning for iframe based editor&#x20;
* Fix CKEditor 4 on Salesforce&#x20;
* Fix "RENDER\_NUNJUCKS" running mod on certain sandboxed iframes
* Prevent insert at cursor from inserting into unfocused frames
* Fix Floating Panel repositioning in nested frames

### :bricks: Bricks

* Add support for running brick sub-pipeline across context (e.g., across tabs)
* The `[Experimental] Insert Text at Cursor`  brick now returns an object with the key `inserted` . Inserted is `true` if text was successfully inserted and `false`if there was no text to insert or if text insertion was attempted in a frame that was not focused


---

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