> 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.1.md). # Release 2.2.1 Release 2.2.1 was published to the Chrome Web Store on December 9, 2024 ### 🎨 User Experience * Introduces icon support for the Text Selection Menu. If a mod developer provides both an icon and an emoji, the emoji will take precedence * Adds support for binary data in the `HTTP Request` brick * Adds blob support to the `[Experimental] Export/Download as File` brick ### :bricks: New Bricks * Introduces new `[Experimental] Streaming HTTP Request` brick to support HTTP Streaming Responses via SSE (server-sent events) ### :bug: Bug Fixes * Fixes a race condition where saving changes on a recently created mod threw an error that the user no longer had access to the mod on slower network connections * Fixes an issue with newer versions of Edge where some Chrome-only APIs were throwing instead of treating the API as a no op * Fixes the Form Preview for the Rich Text Editor in the Page Editor --- # 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.1.md?ask=&goal= ``` `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.