Firefox Architecture & Key Features

Browser Choice

#

While the majority of users rely on Chrome or Chromium-based browsers, Firefox maintains distinct architectural advantages. Key features include native vertical tabs/sidebars, isolated container contexts, preservation of declarative request blocking (MV3), and Gecko-based platform independence.

Sidebar

#

When navigating web browsers like Firefox, tools and extensions present information through two primary UI surfaces: Top Bar Dropdown Popups (Toolbar buttons) and the Vertical Sidebar.

While both interfaces interact with the same underlying browser extensions and data stores, they cater to fundamentally different interaction models: transient micro-interactions versus persistent workspaces.

Architectural Comparison

#

Breakdown by Interaction Pattern

#

1. Top Bar / Extension Popups (Transient Actions)

#

Toolbar extension popups are optimized for high-speed, temporary tasks:

• Auto-Dismissal: The popup UI immediately destroys its temporary view once you click anywhere on the primary web page or switch to a different tab.
• Contextual Awareness: Icons on the top bar dynamically render context badges (e.g., matching password counts in Bitwarden or blocked script counts in uBlock Origin) tied strictly to the domain open in the active tab.
• Best Used For: Standard credential autofill (Ctrl + Shift + L), toggling extensions on/off, or running single-step actions.

2. Firefox Sidebar (Persistent Workspaces)

#

The Firefox Sidebar provides a continuous vertical workspace anchored alongside your web viewport:

• Non-Blocking Execution: You can copy data, edit fields, and organize items inside the sidebar while simultaneously navigating, typing, or scrolling on the main page.
• Vertical Real Estate: Widescreen monitors have excess horizontal space. The sidebar utilizes this space for deep hierarchy views (like nested Bookmark folders, History timelines, or tree-style tab managers).
• State Retention: Navigating between tabs or clicking on page elements does not close or reset the sidebar view.

Firefox Containers

#

Multi-Account Containers separate site data (cookies, local storage, IndexedDB, cache) into distinct, color-coded contextual containers. This allows you to maintain multiple simultaneous sessions on the same domain without cross-container tracking or credential leaks.

Isolated Identity Management

#

• Personal / Main Email: Operates in a dedicated container or default context. Primary identity cookies remain isolated from tracking scripts and secondary accounts.
• Work Email: Configured in a separate “Work” container. Session cookies, OAuth tokens, and enterprise SAML states stay isolated from personal activity.
• Disposable / Checking Email: Isolated inside a lightweight container (e.g., “Regular Check”). Logs into secondary or high-spam accounts without exposing your main profile to tracking pixels or web beacons.

Automatic Site Assignment Rules

#

1. Install the official Firefox Multi-Account Containers extension from Mozilla.
2. Click the Container icon on the toolbar and select Edit Containers to set up custom names, colors, and icons.
3. Open the target domain (e.g., mail.google.com), click the Multi-Account Containers toolbar button, and check Always open in [Container Name].
4. When accessing the domain from a default tab, Firefox intercepts the request and automatically redirects it into its assigned container.

Firefox IP Protection (Built-in Browser VPN)

#

Firefox includes a native, browser-level IP Protection feature (built-in proxy/VPN) designed to hide your public IP address directly within the browser without requiring external software.

Architectural Scope & Limits

#

• Browser-Level Proxy: Traffic routing is isolated strictly to the Firefox network stack (Gecko/Necko). It does not act as a system-wide OS VPN; other applications (terminal, background daemons, or other web browsers) bypass this proxy.
• 50 GB Monthly Transfer Limit: Free usage is capped at 50 GB per calendar month per Mozilla Account. Upon reaching the threshold, IP protection pauses until the next billing cycle.

Activation Procedure (about:config)

#

1. Open the Configuration Page: Type about:config into the address bar and press Enter.
2. Accept the Risk and Continue on the warning screen.
3. Search for the VPN setting: browser.ipProtection.enabled
4. Toggle the value from false to true.
5. Restart Firefox and access the VPN settings via the Toolbar or Settings -> Privacy & Security.

Extension Architecture: Manifest V3 & uBlock Origin

#

While Chromium-based browsers enforce Declarative Net Request (DNR) rules under Manifest V3 (MV3)—limiting dynamic rule counts and background scripts—Firefox maintains a hybrid extension framework.

webRequest API Preservation

#

• Blocking webRequest Support: Chrome MV3 restricts webRequestBlocking in favor of declarative rules. Firefox MV3 retains support for the blocking webRequest API.
• Full uBlock Origin Support: Because Firefox preserves request-level interception capabilities, uBlock Origin (uBO) operates with its full wide-spectrum filtering engine (including dynamic URL filtering, scriptlet injection, and HTML response body modification via =replace) rather than requiring the downgraded uBlock Origin Lite variant.

Mobile Platform Comparison

#

Android SandBox Architecture

#

1. Android Application Sandbox (OS Layer)

#

Like all Android applications, Firefox operates inside Android’s native Linux-based UID application sandbox:

• UID Isolation: The Android OS assigns a unique Linux User ID (UID) to the Firefox main process.
• Storage & Resource Isolation: Storage directories, app data, and hardware peripherals are strictly isolated from other installed apps unless explicit permissions are granted.

2. Process Separation via GeckoView

#

Unlike legacy Firefox Mobile (Fennec), which ran in a single process, the modern GeckoView runtime splits browser components across separate process boundaries:

• UI Process: Handles the Android interface, user inputs, and system calls.
• Child Content Processes: Renders web pages in dedicated background service processes rather than running everything in the application’s primary thread.

3. Fission (Site Isolation)

#

Firefox leverages its Fission architecture on mobile to isolate different website origins into separate renderer processes:

• Prevents cross-site side-channel attacks (e.g., Spectre) by ensuring scripts from site-a.com cannot access memory allocated to site-b.com.
• State of Rollout: Fission is integrated into GeckoView and enabled by default on recent Firefox for Android builds, with toggle controls available under Firefox Labs / about:config.

Comparison: Firefox vs. Chromium Sandbox on Android

#