Skip to content

Verify browser_specific_settings.gecko.strict_min_version is correct #10

Description

@bryanmatthewsimonson

manifest.json declares "strict_min_version": "128.0". This is because we use "world": "MAIN" on a content script (src/page/nip07-bridge.js), which Firefox landed in 128.

Open questions:

  • Is 128 actually correct, or can we go lower by reworking the MAIN-world injection? (e.g. dynamic chrome.scripting.executeScript({ world: 'MAIN' }) on first relay use, which lowered the bar in some other extensions.)
  • Is 128.0 compatible with the current Firefox ESR (128 ESR, yes; 115 ESR, no)? If we care about ESR 115 we need an alternate injection path.
  • Chrome has no floor specified; do we need one? Chrome got MV3 MAIN-world content scripts in 111.

Closing this issue requires: documented rationale in CONTRIBUTING or the manifest comment, ideally with a table of "feature → minimum Firefox/Chrome version".

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Long tailarea/buildCI / packaging / releaseparityTracks userscript feature parity

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions