> 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.10.md). # Release 2.2.10 Published to the Chrome Web Store on May 5, 2025 ### :race\_car: Performance Improvements * Fix memory leak in sandbox and offscreen document error handling code * Eliminate unnecessary sandbox connectivity checks and retries * Eliminate unnecessary retrieval of mod variables for brick configurations that don't reference mod variables, and when getting/setting state * Avoid duplicate triggers on page load caused by Single Page Application navigation ### :art: User Experience * Add support for custom post-uninstall URLs in white label extension builds * Page Editor Version History shortcut to activate a previous version of a mod ### :bricks: Brick Updates * HTTP Request, Streaming HTTP Request: add field to control login nudge behavior if interactive login is required --- # 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.10.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.