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

# Release 1.8.9

Released to the Chrome Web Store on February 20, 2024

### ✨ Enhancements

* Markdown support has been updated to utilize the latest [CommonMark](https://spec.commonmark.org/0.31.2/) spec. This may impact how certain edge cases are rendered. (#[7524](https://github.com/pixiebrix/pixiebrix-extension/pull/7524))
* When a user is prompted to authenticate with PixieBrix from a restricted URL, they are redirected back to the restricted URL after authenticating (#[7624](https://github.com/pixiebrix/pixiebrix-extension/pull/7625))
* Add `disableLoginTab` option to managed storage to disable automatically opening the login tab unless the user navigates to a URL the organization has restricted (#[7619](https://github.com/pixiebrix/pixiebrix-extension/pull/7627))

### 🐛 Bug Fixes

* Fixed issue where users were not automatically redirected from restricted URLs after clearing the PixieBrix token (#[7552](https://github.com/pixiebrix/pixiebrix-extension/pull/7554))
* Selecting one of multiple forms in a render document no longer selects all of them (#[7019](https://github.com/pixiebrix/pixiebrix-extension/pull/7563))
* Fixed a bug where PixieBrix showed an error toast when the last context was removed from a Context Menu starter brick (#[7100](https://github.com/pixiebrix/pixiebrix-extension/pull/7594))
* Fixed a bug during mod activation in the sidebar where a blank panel was shown if there were no other panels (#[7542](https://github.com/pixiebrix/pixiebrix-extension/pull/7596))
* Fixed bug where the managed policy wasn't taking effect on browser profile startup (such as opening Chrome after logging into a VDI) (#[7618](https://github.com/pixiebrix/pixiebrix-extension/pull/7628))
* Fixed bug where the `Set Input Value` brick cleared the whole page in DraftJS editors (#[7630](https://github.com/pixiebrix/pixiebrix-extension/pull/7644))

### 🎨 User Experience

* Improved responsiveness of form and field labels to improve usability of the Page Editor on smaller screens (#[7464](https://github.com/pixiebrix/pixiebrix-extension/pull/7464), #[7558](https://github.com/pixiebrix/pixiebrix-extension/pull/7597))
* Improved loading time of the Extension Console (#[7487](https://github.com/pixiebrix/pixiebrix-extension/pull/7487))
* Improved the "Context Invalidated" experience in the Page Editor (#[7599](https://github.com/pixiebrix/pixiebrix-extension/pull/7599))
* When updating or disabling the Extension, unused starter bricks are removed immediately (#[4258](https://github.com/pixiebrix/pixiebrix-extension/pull/7606))
* Iframes are updated from the Page Editor without a full page reload (#[6648](https://github.com/pixiebrix/pixiebrix-extension/pull/7608))


---

# 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-1.8.9.md?ask=<question>&goal=<user_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.