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

# Release 1.8.8

Released to the Chrome Web Store on February 7, 2024

### ✨ Enhancements

* When a restricted user has new deployments and they navigate to the Extension Console, the deployments are now activated automatically (#[7434](https://github.com/pixiebrix/pixiebrix-extension/pull/7482))
* Add support for sandboxed iframes (#[7300](https://github.com/pixiebrix/pixiebrix-extension/pull/7374))
* Added ability for organizations to set policies to restrict certain URLs when users are not authenticated (#[7483](https://github.com/pixiebrix/pixiebrix-extension/pull/7517))

### 🐛 Bug Fixes

* Fixed a bug where the sidebar sometimes showed up inside iframes (#[7476](https://github.com/pixiebrix/pixiebrix-extension/pull/7490))
* Fixed a bug with the Variable Popover where clicking between variables sometimes failed to reposition the popover (#[7110](https://github.com/pixiebrix/pixiebrix-extension/pull/7479))
* Fixed two other bugs relating to Variable Popover positioning (#[7440](https://github.com/pixiebrix/pixiebrix-extension/pull/7440))
* Fixed a bug where multiple copies of the same error alert were sometimes displayed (#[7353](https://github.com/pixiebrix/pixiebrix-extension/pull/7473))
* Made the mods search case insensitive in the Mods Panel of the Page Editor (#[6839](https://github.com/pixiebrix/pixiebrix-extension/pull/7418))
* The Workshop History tab version dropdown now shows the correct date. Also improved the performance of the dropdown. (#[6455](https://github.com/pixiebrix/pixiebrix-extension/pull/7416))
* Fixed a bug with the textarea `Submit on Enter` functionality where field values set from mod variables was included in the submitted payload (#[7543](https://github.com/pixiebrix/pixiebrix-extension/pull/7549))

### 🧱 New/Updated Bricks

* In the `Custom Form` and `Show a modal or sidebar form` bricks, added support for adding placeholder text to inputs (#[7432](https://github.com/pixiebrix/pixiebrix-extension/pull/7433))
* The `Render Document`, `Custom Form`, and `Show a modal or sidebar form` bricks now include an `Advanced: Theme` section where developers can add custom CSS stylesheets (#[7499](https://github.com/pixiebrix/pixiebrix-extension/pull/7501), #[7492](https://github.com/pixiebrix/pixiebrix-extension/pull/7506), #[7493](https://github.com/pixiebrix/pixiebrix-extension/pull/7507), #[7494](https://github.com/pixiebrix/pixiebrix-extension/pull/7508), #[7495](https://github.com/pixiebrix/pixiebrix-extension/pull/7513), #[7496](https://github.com/pixiebrix/pixiebrix-extension/pull/7515), #[7497](https://github.com/pixiebrix/pixiebrix-extension/pull/7516), #[7498](https://github.com/pixiebrix/pixiebrix-extension/pull/7550))

### 🎨 User Experience

* Activation links can now include activation options as part of the url (#[7478](https://github.com/pixiebrix/pixiebrix-extension/pull/7510))


---

# 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.8.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.
