search

microsoft / MicrosoftEdge-Extensions

This is a community space for Microsoft Edge Add-ons developers, to share resources and information about building, publishing and growing their Microsoft Edge extension.
MIT License
141 stars 128 forks source link

match_origin_as_fallback is not working in Edge Manifest V3 extension #162

Open GaurangTandon opened 3 months ago

GaurangTandon commented 3 months ago

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:

image

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 commented 3 months ago

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