Repository navigation
fix: Pass matchOriginAsFallback to content scripts registered in dev mode - #2737
Conversation
…v mode In MV3 dev mode, content scripts are registered with the scripting API instead of the manifest, and the option was dropped on the way. A script with `matchOriginAsFallback: true` ran in about:, blob: and data: frames in a production build but not under `wxt dev`.
✅ Deploy Preview for creative-fairy-df92c4 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
|
…script-registrations
@wxt-dev/analytics
@wxt-dev/auto-icons
@wxt-dev/browser
@wxt-dev/i18n
@wxt-dev/is-background
@wxt-dev/module-react
@wxt-dev/module-solid
@wxt-dev/module-svelte
@wxt-dev/module-vue
@wxt-dev/runner
@wxt-dev/storage
@wxt-dev/unocss
@wxt-dev/webextension-polyfill
wxt
commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2737 +/- ##
==========================================
- Coverage 80.23% 80.21% -0.03%
==========================================
Files 140 140
Lines 4175 4175
Branches 968 968
==========================================
- Hits 3350 3349 -1
Misses 725 725
- Partials 100 101 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Thanks for helping make WXT better! |
Overview
In MV3 dev mode, content scripts are registered with the scripting API instead of the manifest, and the option was dropped on the way. A script with
matchOriginAsFallback: trueran in about:, blob: and data: frames in a production build but not underwxt dev.Manual Testing
Demo extension package included that shows where scripts are inserted. The difference between development and production builds for matchOriginAsFallback is gone after this PR.
Before:

After:

Demo extension:
wxt-match-origin-as-fallback-demo.tar.gz