# PixieBrix Browser Extension 2.0.0 Migration Guide {% embed url="" %} We're excited to announce the upcoming PixieBrix Browser Extension 2.0.0 release! The release will be published to the Chrome Web Store in May 2024. * Migrates the PixieBrix Browser Extension to use [Web Extensions Manifest V3](https://developer.chrome.com/docs/extensions/develop/migrate), which brings additional web extension performance and security guarantees * The PixieBrix Sidebar now uses the [Chromium Side Panel](https://developer.chrome.com/docs/extensions/reference/api/sidePanel), which is separate from the host page * Official Microsoft Edge Add-ons listing to simplify distribution ### Upgrading to PixieBrix Browser Extension 2.0.0 * No special steps are required **—** when the PixieBrix Browser Extension 2.0.0 is published to the Chrome Web Store, your browser extension will automatically upgrade ### Testing the Upcoming 2.0.0 Release {% hint style="warning" %} The PixieBrix BETA channel extension is a different extension listing as the main PixieBrix extension. Running both at the same time will cause the extensions to malfunction. {% endhint %} {% hint style="info" %} Mods and Local Integrations manually configured in the main PixieBrix extension *will not* transfer to the PixieBrix BETA extension. You will need to re-activate any mods for use in the PixieBrix BETA extension.\ \ Team Deployments will automatically activate as normal. {% endhint %} * Uninstall or disable the PixieBrix browser extension * Activate the [PixieBrix BETA browser extension from the Chrome Web Store](https://chromewebstore.google.com/detail/pixiebrix-beta/mpapkmgkphbggmlekkfnoilmafnbfile) #### Enterprise: Allowlisting the BETA channel extension If you are an enterprise-managed device, you may need to have your IT team allowlist the PixieBrix BETA channel extension. The PixieBrix BETA channel extension id is: ``` mpapkmgkphbggmlekkfnoilmafnbfile ``` See [Browser Extension Installation Policy](/enterprise-it-setup/browser-extension-installation-and-configuration/browser-extension-installation-policy.md) for more information on allowlisting the extension. #### Enterprise: Allowlisting the BETA OAuth2 PKCE redirect URL If you are using a custom OAuth2 PKCE integration with PixieBrix, you will need to update the Redirect URLs for your OAuth2 integration to support the BETA channel extension id redirect URL: ``` https://mpapkmgkphbggmlekkfnoilmafnbfile.chromiumapp.org/* ``` See [Advanced: Custom Integrations](/integrations/advanced-custom-integrations.md) for more information on configuring OAuth2 PKCE integrations. ### System Requirements * PixieBrix *officially supports* the last two major version of Chrome (Chrome 124 and 125). Supporting the last two versions ensures the PixieBrix extension has access to the latest security and bug patches. * *Unofficially, the PixieBrix 2.0.0 release may work on Chrome 116 and later*. Chrome 116 contains all of the required web extension APIs. However, we do not test PixieBrix on old versions of Chrome and there may be bugs and/or performance problems. ### PixieBrix Extension User Experience Changes * The PixieBrix Sidebar uses the Chromium Side Panel: * Note: Microsoft Edge's tab-specific side panel behavior is inconsistent with Chrome. On Microsoft Edge, [the side panel closes if you switch to another tab](https://github.com/w3c/webextensions/issues/588) * Note: Microsoft Edge's side panel extension content script behavior is inconsistent with Chrome. On Microsoft Edge, [the PixieBrix content script is not loaded in iframes embedded in the side panel](https://github.com/w3c/webextensions/issues/616#issuecomment-2115358648) * The PixieBrix Sidebar requires a user gesture to open (e.g., button click): * The user gesture requirement is a Chromium Side Panel policy * If there is a delay between a user gesture and opening the sidebar (e.g., an API call), PixieBrix will display a dialog prompting the user to click to open the sidebar ### PixieBrix Mod Developer User Experience Changes * The Chromium Side Panel will shrink the available space for the Page Editor. If working on a small screen, we recommend [undocking the Chrome DevTools into a separate window](https://developer.chrome.com/docs/devtools/customize#placement): \ ![](/files/eDNTrULy5gmJrvWegbiA) ### PixieBrix Extension Internal Changes * All text templates are now evaluated in a sandbox iframe. Previously, you had to toggle on sandboxed template evaluation in the Extension Console > Settings page. * Sandboxing should not impact mod behavior. However, you should verify your mods continue to work. In rare cases, a host page may interfere with the sandbox iframe ### Reporting Bugs To report bugs or performance issues, contact , or post a message [in the Community Slack](http://slack.pixiebrix.com) ### Known Issues For an up-to-date list of known issues impacting Chromium MV3 and Microsoft Edge support, use the following GitHub reports: * [Chromium MV3](https://github.com/pixiebrix/pixiebrix-extension/issues?q=is%3Aissue+is%3Aopen+label%3Amv3) * [Microsoft Edge](https://github.com/pixiebrix/pixiebrix-extension/labels/edge) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.pixiebrix.com/release-notes/release-notes-archive/pixiebrix-browser-extension-2.0.0-migration-guide.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.