> 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.8.md). # Release 2.2.8 Published to the Chrome Web Store on March 31, 2025 ### :art: User Experience * Users will now only receive deployments that have a Platform set to Browser Extension or the value is unset. This is a backwards compatibile change that will not impact existing deployments * Prevent the Extension from running in PixieBrix Web App contexts * Improves the positioning of the Action Menu and Text Selection Menu on Microsoft Word by preventing the menus from overlapping each other * Introduces a new Renderer Version under the `Advanced: Theme`section of the Document Renderer brick. This new renderer simplifies the DOM structure and eases adding custom CSS but can result in visual discrepancies in mods that were built with the original version (v1). New mods still default to v1 --- # 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.8.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.