Examine source code of Mobile Startup Homepage

{
  "manifest_version": 2,
  "name": "Mobile Startup Homepage",
  "version": "2.0",
  "description": "A real homepage for Firefox on Android: opens the page you choose when the browser starts, plus a Home button. Mobile Firefox has no homepage setting - this adds one.",
  "_mv2_note": "⛔ MANIFEST V2 ON PURPOSE, and it is the whole reason this version exists. v1.0 was MV3, whose background is a NON-PERSISTENT event page by design - and MEASURED 2026-08-11 on the real phone, Firefox for Android never wakes that event page at browser start, so neither `runtime.onStartup` nor the top-level fallback ever ran and the homepage silently did nothing. (The toolbar button worked throughout, which is what proved the trigger was the only broken part.) MV2 `persistent: true` loads the background page AT BROWSER START, which is exactly the missing behaviour; Firefox still fully supports MV2, and uBlock Origin runs this way on Android. ⚠ Do not 'modernise' this back to MV3 without re-testing startup on a real Android device - the platform, not the manifest version, is what decides.",
  "browser_specific_settings": {
    "gecko": {
      "id": "mobile-startup-homepage@addons.local",
      "strict_min_version": "128.0",
      "_data_note": "⛔ MANDATORY for new add-ons since 2025-11-03; AMO rejects the signing request without it. `none` is the truthful answer here and must be the ONLY entry - it cannot be combined with any other value. This add-on stores one URL in storage.local on the device and transmits nothing: no host permissions, no content scripts, no network calls of its own, and storage.local deliberately rather than storage.sync so the address never reaches a Mozilla server.",
      "data_collection_permissions": {
        "required": [
          "none"
        ]
      }
    },
    "gecko_android": {
      "strict_min_version": "128.0"
    }
  },
  "_permissions_note": "tabs ONLY, and only to READ the active tab's url so that a blank startup tab can be reused instead of a new one being piled on at every launch. Without it tab.url is undefined and the extension would have to create a tab every time. No host permissions: it never reads or touches page CONTENT, only navigates. storage keeps the one URL you configure - deliberately local, never sync, so the address is not copied to a Mozilla server.",
  "permissions": [
    "tabs",
    "storage"
  ],
  "_url_note": "⛔ NO URL IS BAKED IN. The add-on ships blank and is configured after install. That is what keeps a private address out of the package uploaded to Mozilla for signing.",
  "background": {
    "scripts": [
      "background.js"
    ],
    "persistent": true
  },
  "options_ui": {
    "page": "options.html",
    "open_in_tab": true
  },
  "browser_action": {
    "default_title": "Go to homepage",
    "default_icon": {
      "48": "icon.svg",
      "96": "icon.svg"
    }
  },
  "icons": {
    "48": "icon.svg",
    "96": "icon.svg"
  }
}