Early HTML5 Collaboration: Chromium, Mozilla, and Apple

In the mid-to-late 2000s, the future of the web was shaped by an unprecedented alliance between major browser vendors. This article explores how the Chromium team collaborated with Mozilla and Apple through the Web Hypertext Application Technology Working Group (WHATWG) to create the HTML5 specification. By sharing code, aligning on new web APIs, and prioritizing real-world implementation over theoretical standards, these competitors united to modernize the internet and replace aging proprietary technologies with open web standards.

The Formation of WHATWG and Chromium's Entry

In 2004, representatives from Apple, Mozilla, and Opera formed the WHATWG. They were frustrated with the World Wide Web Consortium (W3C) and its decision to abandon traditional HTML in favor of the strict, XML-based XHTML 2.0. The WHATWG wanted to evolve HTML incrementally to support modern web applications without breaking existing websites.

Google soon joined this effort and hired Ian Hickson, the primary author and editor of the HTML5 specification. When Google launched the open-source Chromium project in 2008, HTML5 was its foundational pillar. The Chromium team immediately dedicated massive engineering resources to the WHATWG, working directly alongside Mozilla and Apple to turn the theoretical specification into a working reality.

Shared Codebases: Chromium and Apple’s WebKit

The collaboration between the Chromium team and Apple was uniquely tight-knit because they shared the same rendering engine. Instead of building a new engine from scratch, the Chromium team chose to use Apple’s open-source WebKit engine.

For several years, Chromium and Apple engineers worked side-by-side in the exact same codebase. They divided the labor of implementing early HTML5 features. When Chromium engineers wrote code to support HTML5 forms, WebSockets, or local storage in WebKit, Apple’s Safari browser inherited those features. Conversely, Apple’s work on hardware-accelerated CSS and media playback directly benefited Chromium. The two teams reviewed each other's code daily, fixing bugs and refining the HTML5 specification based on what they learned during implementation.

Cross-Pollination of Features with Mozilla

While Chromium and Apple shared WebKit, Mozilla used its own rendering engine, Gecko. Collaboration with Mozilla focused on API design, security, and interoperability. A pattern emerged where one vendor would invent a feature, and the others would collaborate to standardize and improve it.

For example, Apple originally invented the <canvas> element for its macOS Dashboard widgets. Mozilla and Chromium engineers worked with Apple through the WHATWG to strip out proprietary behaviors, write a formal specification, and implement the 2D drawing API identically across both Gecko and WebKit. Similarly, Mozilla’s early experiments with offline web applications and audio/video integration heavily influenced the <video>, <audio>, and localStorage specifications that Chromium and Apple subsequently adopted and helped refine.

Unifying the HTML Parser

Before HTML5, every browser handled broken or invalid HTML code differently. This forced web developers to write frustrating, browser-specific workarounds. One of the greatest achievements of the Chromium, Mozilla, and Apple collaboration was the creation of a unified HTML5 parsing algorithm.

Led by Ian Hickson at Google, the teams analyzed billions of web pages to reverse-engineer how browsers handled bad code. Mozilla engineer Henri Sivonen developed the first complete HTML5 parser based on this data. Rather than reinventing the wheel, the Chromium and Apple teams collaborated closely with Mozilla to port those exact parsing rules into WebKit. By sharing test suites and edge-case data, the three teams ensured that Chromium, Firefox, and Safari would generate the exact same Document Object Model (DOM) from the same HTML code, even if that code was broken.

Real-Time Communication and "Running Code"

The day-to-day collaboration bypassed traditional, slow-moving committee meetings. Instead, engineers from Chromium, Mozilla, and Apple communicated in real-time on the public #whatwg IRC channel and open mailing lists.

Decisions were governed by the philosophy of "rough consensus and running code." If a Chromium engineer proposed a new HTML5 feature, Mozilla and Apple engineers would critique its security, performance, and developer usability within minutes on IRC. A feature was only kept in the HTML5 specification if the browser vendors proved they could implement it successfully. If Chromium, Mozilla, or Apple hit a technical roadblock while coding a feature, the specification was quickly rewritten to match reality. This rapid feedback loop between the three teams allowed HTML5 to mature quickly and become the definitive standard for the modern web.