match_origin_as_fallback is not working in Edge Manifest V3 extension

[GaurangTandon]

When we upload our item containing the following "content_scripts" key in our manifest.json:

  "content_scripts": [
    {
      "matches": [
        "<all_urls>"
      ],
      "js": [
        "js/scriptA.js",
        "js/scriptB.js",
        "js/scriptC.js"
      ],
      "match_origin_as_fallback": true,
      "match_about_blank": true,
      "all_frames": true,
      "run_at": "document_idle"
    }
  ],

We get this error:

When we remove match_origin_as_fallback and then reupload, then the upload works successfully.

The documentation on this (link) is sparse and it redirects to the Chrome documentation, which does in fact support this property (link here). On MDN Docs it says the property is supported since Edge 99, although as shown above we couldn't get it to work.

Here's the link to the full manifest file that did not work for us. Could anyone please elaborate what is the issue here exactly?

[ManikanthMSFT]

Hi @GaurangTandon, thank you for reporting this. We are looking into this and will let you know as soon as we have an update.

[cuyler-at-scribe]

We got the same warning when uploading a new version of our extension that also uses this property.

Is this issue still active?

[carlosjeurissen]

@ManikanthMSFT it is surprising to see the permissions and content_security_policy keys being supported for content_scripts objects. Is there documentation for this?

@cuyler-at-scribe were you able to upload the extension and get it reviewed? Or is it still blocking the upload?

[Rahul-Bauri]

Hi @GaurangTandon @cuyler-at-scribe

I am Rahul from the Microsoft Edge Extensions Developer Support team.

Apologies for the delayed response. Could you please check and confirm whether the issue related to the match_origin_as_fallback property in the content_scripts key of your manifest.json file, which was causing an upload error, has been resolved? If you're still experiencing the issue, please let me know so I can escalate it to the appropriate team and assist in resolving the bug. Otherwise, I’ll proceed to close this issue upon your confirmation. Thank you!

[Rahul-Bauri]

Closing this issue for now as we haven’t received any response from you. If you encounter the problem again in the future, please feel free to raise a new bug so we can assist you further with the resolution.

[ashwin-blaze]

Hi @Rahul-Bauri, getting this warning even though the upload succeeded.

[carlosjeurissen]

@Rahul-Bauri is there a specific reason the partner dashboard applies a stricter set of features compared to the browser? It seems to often cause issues like the one above.