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 126 forks source link

[Bug - Partner Center] Manifest validation error for valid "world": "MAIN" property in content_scripts #180

Open ouweiya opened 1 month ago

ouweiya commented 1 month ago

Describe the bug The Microsoft Partner Center is throwing a validation error for a legitimate "world": "MAIN" property in the content_scripts array of the manifest file. This property is part of the standard Web Extensions API and should be accepted.

To Reproduce Steps to reproduce the behavior:

  1. Go to the Microsoft Edge Addons developer dashboard
  2. Attempt to upload a browser extension with a manifest file containing "world": "MAIN" in the content_scripts array
  3. Observe the validation error

Expected behavior The manifest file should be accepted without errors, recognizing "world": "MAIN" as a valid property in content_scripts.

Screenshots image

Error message

The following checks failed:
Package acceptance validation error: The manifest shouldn't contain the key field.
Warnings:
Package acceptance validation warning: Only the following properties are allowed in the object: matches, exclude_matches, css, js, match_about_blank, run_at, all_frames, include_globs, exclude_globs, permissions, content_security_policy. Code: content_scripts[0].world: MAIN Line: 21 Column: 20

Desktop (please complete the following information):

Additional context The "world": "MAIN" property in content_scripts is a valid part of the Web Extensions API, used to specify the JavaScript world in which the content script should run. It's supported by major browsers including Chrome and Firefox. This validation error in the Edge Addons website prevents developers from using this legitimate feature in their extensions.

References

ManikanthMSFT commented 1 month ago

Hi @ouweiya,

Thank you for reporting this. We are looking into this and will let you know as soon as we have an update.

ouweiya commented 4 weeks ago

Hi @ManikanthMSFT

Thanks for your work on this issue. 👋

I'm reaching out about the timeline for this bug fix. It's become a blocker for us:

Could you share an estimated timeframe for the fix? This would really help with our release planning.

Let me know if you need any more info from our side to help resolve this. Happy to provide whatever's needed.

Thanks in advance for your help on this! 🙏

ManikanthMSFT commented 3 weeks ago

Hey @ouweiya, our team is actively working on resolving this issue. We understand the impact it has on your release process and are prioritizing it accordingly. We expect to have an update for you by the end of next week.

ouweiya commented 2 weeks ago

@ManikanthMSFT

Hello Manikanth,

I'm following up on the issue we previously discussed.

I wanted to inform you that I attempted to replicate the scenario again today, and unfortunately, the problem still persists. I was wondering if there have been any developments or progress made regarding this issue since our last communication.

Additionally, I would greatly appreciate any new suggestions or valuable information you might be able to provide to help address this ongoing concern.

ManikanthMSFT commented 1 week ago

Hey @ouweiya, to better assist you, could you please provide us with your zip package? You can send it to our email address [ext_dev_support@microsoft.com]. Our engineering team will review it and get back to you with the necessary assistance. Also, we recommend you mention #180 for our reference.