> 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.5.md). # Release 2.2.5 Published to the Chrome Web Store on February 18, 2025 ### 🎨 User Experience * Reduces the amount of time before Extension functionality is reinjected in CKEditor4 on Salesforce * Adds support for setting the icon in temporary sidebar panels * Adds a prioritiy option to the `AddFloatingActionEffect`for ordering floating actions * Adds a priority option to the `Context Menu`starter brick for ordering context menu items * When audio capture is started, the Extension will emit the `audio-capture:started` event so mod developers can manage state as needed * When audio capture is stopped due to web navigation or tab closure events, the Extension will emit the `audio-capture:stopped`event so mod developers can manage state as needed ### :bug: Bug Fixes * Fixes several edge cases around tracking focus on the host page while the Floating Panel is open, especially when the selected text is in an iframe * Fixes issue with the Action Menu icons not loading or loading with the wrong color * Fixes issue where the `[Experimental] Streaming HTTP Request` failed to show the login banner for configured requests that require authentication when the request returns a 401 or 403 * Fixes a UI issue in the Page Editor which caused long icon names in the icon picker to overflow onto and obscure the options below them on smaller width screens --- # 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.pixiebrix.com/release-notes/release-notes-archive/release-2.2.5.md?ask=&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.