[FeatureReq - Partner Center] Enable cross-browser V3 manifests
**Is your feature request related to a problem?
We encountered this warning:
The issue is that we want to be able to use the same manifest for Firefox, which has different requirements. So from our point of view the validation in the Microsoft Edge store is too strict. Note that the Chrome store doesn't do such strict validation either.
Firefox still uses "scripts" https://stackoverflow.com/questions/75043889/manifest-v3-background-scripts-service-worker-on-firefox/78088358#78088358
Hence we changed our manifest from
"background": {
"service_worker": "js/background.bundle.js",
"type": "module"
},
To
"background": {
"service_worker": "js/background.bundle.js",
"scripts": ["js/background.bundle.js"],
"type": "module"
},
to still support Firefox after the v3 migration.
Describe the solution you'd like
Ignore scripts in background if service_worker is present and pointing to the first element in a single element array in scripts
Describe alternatives you've considered
Ignore scripts in background
Additional context
Hi @lsmith77, thank you for suggestion. We have forwarded your feedback and the proposed solution to our engineering team. They are currently reviewing it.
We understand the importance of this issue and once we have an update or need further information, we will get back to you promptly. We appreciate your contribution to improving the platform.
This is not specifically an Edge issue. Mozilla and Chrome don't seem to have agreed on the specific syntax, which as you pointed out, is different for both browsers. Edge is based on Chromium and will expect the Chrome syntax.
You will have to have 2 manifest.json file and build separate packages for Mozilla vs Chome/Edge.
Mozilla and Chrome don't seem to have agreed on the specific syntax
No, they did, as of versions 121:
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/background#browser_support
More info/links in #172
Hi @lsmith77 @FMaz008 @ghostwords
I am Rahul from the Microsoft Edge Extensions Developer Support team.
This feature request aligns with item https://github.com/microsoft/MicrosoftEdge-Extensions/issues/136, so I’m closing this as a duplicate. All future updates related to this feature will be tracked under https://github.com/microsoft/MicrosoftEdge-Extensions/issues/136. Thank you for your understanding.