Proposal: Support Extended "browser_specific_settings"

[erosman]

Proposal: Support Extended "browser_specific_settings"

Background

Although the general consensus aims towards the unification of the manifest.json between browsers, there are properties that would remain browser-specific, nonetheless.

Proposal

The proposal is in two parts:

• Support "browser_specific_settings"
• Extend the coverage

Use Cases

1. strict min/max version

As mentioned in #115, set per browser "strict_min_version", "strict_max_version".

2. "background"

As discussed in #282, set "background", thus eliminating the need for "preferred_environment" e.g.

{
  
  "browser_specific_settings": {
    "firefox": {
      "background": {
        "scripts": ["background.js"],
        "type": "module"
      }
    },
    
    "chromium": {
      "background": {
        "service_worker": "worker.js",
        "type": "module"
      }
    },

    "opera": {
      "background": {
        "scripts": ["background.js"],
        "type": "module"
      }
    }
  }

}

3. Any property

Browsers to allow and apply any valid property that requires per-browser setting

{
  
  "browser_specific_settings": {
    "firefox": {
      "background": {
        "scripts": ["background.js"],
        "type": "module"
      },
      "icons": {
        "16": "icon.svg",
        "32": "icon.svg",
        "48": "icon.svg",
        "64": "icon.svg",
        "128": "icon.svg"
      },
      "permissions": [
        "browserSettings",
        "contextualIdentities"
      ],
      "strict_min_version": "14",
      "strict_max_version": "20"  
    },

    "chromium": {
      "background": {
        "service_worker": "worker.js",
        "type": "module"
      },      
      "icons": {
        "16": "icon.png",
        "32": "icon32.png",
        "48": "icon48.png",
        "64": "icon64.png",
        "128": "icon128.png"
      },
      "permissions": [
        "pageCapture"
      ],
      "strict_min_version": "14",
      "strict_max_version": "20" 
    }
  }

}

[fregante]

IMHO If a developer needs this, they should just ship separate extensions. There's no need to place everything in one file if there's no overlap.