microsoft / microsoft/MicrosoftEdge-Extensions

[Feature Request - Partner Center] WebExtension with `background.scripts` and `key`

Open
#136 5 comments 9 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Feature Partner Center Tracked
Dominant language
JavaScript
Stars
245
Forks
149
PR merge metrics
No merged PRs in 30d

Description

Describe the bug

Microsoft Partner Center refuses to publish an extension with the background.scripts and key property in manifest V3.

I tried to publish my Cast Kodi extension which has two backgrounds specified in the manifest:

{
  "manifest_version": 3,
  "name": "Cast Kodi",
  "...": "...",
  "background": {
    "service_worker": "background.js",
    "scripts": ["background.js"],
    "type": "module"
  },
  "...": "...",
  "key": "MIIBIjANBg..."
}

Thanks to the Proposal: declaring background scripts in a neutral way w3c/webextensions#282 issue, I can use the same manifest for Chromium and Firefox.

  • Firefox Browser Add-ons accepts manifest with background.service_worker and key.
  • Chrome Web Store accepts manifest with background.scripts.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Microsoft Partner Center > Edge
  2. Publish an extension with the background.scripts and key property in manifest V3.
  3. See error

The following checks failed:

  • Package acceptance validation error: The background.scripts field cannot be used with manifest version 3. Use the background.service_worker field instead. Error code: background: { "service_worker": "background.js", "scripts": [ "background.js" ], "type": "module" } Line: 30 Column: 17
  • Package acceptance validation error: The manifest shouldn't contain the key field.

Expected behavior

Microsoft Partner Center accepts extension with the background.scripts and key property in manifest V3.

Desktop (please complete the following information):

  • OS: Ubuntu 22.04.3 LTS
  • Browser: Firefox
  • Version: 122.0.1

Additional context

Related issues

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.