Firefox Codebase & Tech

The Mozilla Firefox source code (likely the mozilla-central repository) is a massive, complex codebase that builds the Firefox web browser and its underlying technologies.

Source Code Structure

Firefox follows a component-based architecture, generally split into the "Core Engine" (Gecko) and the "Frontend" (UI).

Frontend (The UI)

Located primarily in browser/ and toolkit/. The user interface is built using web technologies: HTML (XHTML), CSS, and JavaScript. It communicates with the core engine through internal APIs (XPCOM/WebIDL).

• browser/: Firefox specific UI code (chrome).
• toolkit/: Shared UI components used by Thunderbird/Firefox.

Gecko (The Rendering Engine)

This is the heart of the browser, responsible for parsing HTML/CSS, executing scripts, and painting content.

• layout/: Calculates where elements go on the page.
• dom/: Implements the Document Object Model APIs (what JS talks to).
• gfx/: Graphics handling (WebRender, layers).
• netwerk/: Networking library (Necko) handling HTTP, DNS, etc.

SpiderMonkey (The JavaScript Engine)

Located in js/src. This is the standalone engine that executes JavaScript code, including the interpreter, JIT compilers (IonMonkey, Warp), and garbage collector.

Infrastructure & Tools

• mach: The Python-based CLI command center for building and developing.
• Taskcluster: CI/CD and distributed testing systems.
• driver/: Code for geckodriver (WebDriver).

Technologies Used

• C++ (C++17/20): The dominant language for the core engine (Gecko), DOM, and SpiderMonkey.
• Rust: Increasingly used for memory-safety critical components like Stylo (CSS parser), WebRender, and various system components.
• JavaScript (ES6+): Used for the entire browser frontend (UI) and simulating browser behavior in tests.
• Python (3.x): Used extensively for the build system (mach), test harnesses, and infrastructure scripts.
• HTML/XHTML & CSS: Used to define the browser's own UI (chrome).
• XPCOM: A legacy modularity system allowing cross-language calls (C++ <-> JS), though this is being modernized/replaced by WebIDL bindings.