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

# Release 3.3.0

Published to the Chrome Web Store on August 26, 2026

#### :sparkles: Enhancements

* Security Policies:
  * AI Prompt, Prohibited Language, Clipboard, and Page-Pattern rules now enforce inside iframed editable fields, including the Salesforce email composer (CKEditor4)
  * Security and compliance notifications now differentiate the four states — warn, action block, soft block, and navigation block — by more than color, adding a header\
    band with a severity pill and tier icon plus a colored accent bar (WCAG)
  * Security Policies: blocked-site (URL) rules now support a configurable severity

#### :bug: Bug Fixes

* Bricks:
  * A brick with an optional sub-pipeline left empty no longer throws
  * Parse URL / Regex: no longer log an output-validation error when the brick legitimately returns no value (e.g., a URL with no host)
  * Add Dynamic Text Snippet / Add Text Snippets: guard against a blank keyboard shortcut
* Triggers:
  * A trigger configured without a selector is now reported as a configuration error instead of a generic failure
  * A trigger whose target-element wait is superseded is no longer logged as a failure
  * Avoids attaching duplicate document-level listeners for triggers on the same page
* Floating Action Button: keeps rendering when the per-site disable setting is stored in an unexpected format on the partner backend
* HTTP Requests: re-reads credentials before sending, so background requests are no longer sent unauthenticated after a cold start
* Admin Console: the Activity Policies table search box now filters the list
* Security Policies: hard-block notices now appear in the lower-right security card, matching where warn notices already appear, instead of a top-center toast


---

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