Firefox WebExtensions and Chromium-style MV3: how long can one extension target both manifest formats?
Integration boundary We maintain a cross-browser extension built on the WebExtensions API (browser.* / chrome.*) that currently ships as Manifest V2. Firefox supports MV3 while also committing to continued MV2 support, whereas Chromium is moving to deprecate MV2. We need to decide how to structure the codebase across this boundary. Constraints and uncertaint