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

# Release 3.3.1

Published to the Chrome Web Store on September 9, 2026

#### :sparkles: Enhancements

* Page Editor:
  * Detect an Element on a Page: the Selector field now offers the selector toggle and element picker, matching bricks like Hide and Show Element (also applied to the deprecated Vue "Set values" brick).
* Security:
  * A Site Access rule can now set the block and soft-block overlay title, not just the body message.

#### :bug: Bug Fixes

* Page Editor: The Page Editor no longer auto-runs previews for Local AI bricks, which could start a background model download.
* Integrations: Fix bug where a deferred integration-login banner or modal could remain after a completed login
* Floating Panel: The floating panel no longer loses focus on pages that trap it, such as Jira's issue-details modal.
* Network Errors: A request that hits the client timeout now reports a timeout instead of a blocked-request error.
* Runtime: After a mod restart, an already-open single-page-app tab re-initializes when you switch to it, instead of needing a manual refresh
* Security Events:
  * Prohibited Language now flags a term even when it touches a symbol, like a trailing "!" or "©"
  * Data Loss Prevention: a warning about flagged content now appears once and can be dismissed, instead of coming back on every keystroke.
  * Soft Block: when a rule offers preset justification reasons, a free form response is not required
  * URL Soft Block: an acknowledgement now applies to the site that matched. Moving within that site no longer re-prompts, and leaving it re-prompts on the next visit.
  * Protected-field detection now keeps working after a bfcache page restore.


---

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