> 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-3.3.4.md). # Release 3.3.4 Published to the Chrome Web Store on October 19, 2026 #### :sparkles: Enhancements * Activity Tracking & DLP: * File-Upload rules: now enforce uploads made inside iframes and embedded editors, with the block prompt and notification shown on the top page * Address Fraud: rules now apply to address forms rendered inside iframes * Page Editor: * New analysis rule to warn on blank Mod Variable Name (Run with Cache, Run with Async Mod Variable) or a blank Date (Parse date) while editing #### :bug: Bug Fixes * Activity & Security Policies: * Print Protection: a protected frame stays blanked after its document is replaced, such as the Salesforce email composer * URL Blocking: a blocked site now shows its block screen once a security dialog that preempted it closes * Bricks: * Stylesheets: the brick now removes its font-face stylesheet on unmount, so long-lived tabs no longer accumulate stylesheets * Rich Text field: fix image insert, paste, and drop failing with "Failed to upload image" when the form is shown as a modal * Page Editor: show a clear message when saving a package that is shared with a team you are not a member of --- # 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-3.3.4.md?ask=&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.