Roadmap
We are still building the foundation. This page shows the current stage, the checks we can repeat today, and the work between us and a first public release.
Verified WPT history
Galileo starts at a verified Servo commit, so both lines share the same first result. The next checkpoint measures each project separately against the same 286 named subtests.
Servo ↔ GalileoEngine · Phase 0 Core
Every point uses the same 286 named subtests. The scale starts at zero, and the latest values remain an upstream reference—not a general browser score or a controlled benchmark.
Swipe horizontally to inspect the full graph.
Loading verified chart.
| Checkpoint | Servo | GalileoEngine | Evidence |
|---|---|---|---|
| Fork · 24 Jul | 246 / 286 | 246 / 286 Inherited identical source | Servo run 30115162450 Extracted baseline |
| 13–14 Aug | 246 / 286 | 286 / 286 | Servo run 31788413088 Comparison data |
The first Galileo value is inherited from the exact Servo commit at the verified merge base; it is not a separate Galileo run. The latest Galileo and Servo captures used different Linux environments, so the second checkpoint is an upstream reference—not a controlled benchmark or a web-compatibility percentage. Inspect the complete series data.
Feature evidence / 68 tracked items
“Observed, partial” means that some behaviour exists. It is not the same as a passed qualification test.
Same-denominator WPT reference
The three test identifiers and all 286 subtest names match exactly. The captures used different Linux environments and profiles, so this is a real upstream reference. It is not a controlled benchmark and not a web-compatibility score.
Servo relationship
93d8f85503e386904a38308The 248 commits measure movement in Servo after the common base. They do not prove that GalileoEngine is “248 commits behind”.
The first graph point comes from Servo's successful public run at commit 93d8f85503e, the verified Galileo merge base. Galileo's first value is deliberately labelled as inherited: at that point the two projects share the same source revision, so the site does not pretend that a second browser run occurred.
The feature view counts all 68 rows in the reviewed Galileo feature inventory. The WPT view reports only the selected phase0-core shard. Galileo's retained report was produced at commit d0e89798d992; Servo's latest value was extracted from the public run at commit 386904a38308. Across both checkpoints, the three test identifiers and all 286 ordered subtest names match. Because the latest execution environments differ, that point remains an upstream reference rather than a controlled benchmark.
Future updates fail closed: when collection fails, the graph keeps the last verified point instead of drawing a guessed line. Each new point must name both commits and link to retained evidence.
View the weekly snapshot · View the graph data · Inspect the fork baseline · Inspect the latest comparison · Open the Servo base commit
Development path
We are working through the foundation now. Later stages begin only when the earlier work is stable enough to support them.
Make builds repeatable and document the browser we inherited from Servo.
Test rendering, navigation, storage, media, and the desktop shell.
Expand standards, real-site, security, privacy, and accessibility work.
Build installation, updates, rollback, recovery, and platform integration.
Release a clearly scoped first build after the required checks pass.
The highlighted step is where most of the work is happening now. Some tasks in the next step have already started.
Current capability
These are development checks, not a promise that the browser is ready for general use.
On a smaller screen, swipe the table horizontally to compare every column.
| Area | What works | State | Important limit |
|---|---|---|---|
| Development build | The current desktop shell builds and launches in our development environment. | Working | There is no signed installer or release package. |
| Rendering & navigation | Selected local and HTTPS pages render, with repeatable navigation, search, and back-navigation checks. | Working | This covers selected tasks, not the wider web. |
| Browser shell | The current Servo shell provides basic browser behaviour for development. | Partial | Many everyday workflows and recovery paths are unfinished. |
| Compatibility automation | Selected WebDriver, standards, cache, and browser API checks can be repeated. | Started | We do not have a complete compatibility score yet. |
| Media | Selected media configurations and muted streaming-video playback have been tested. | Started | Audio, seeking, adaptive playback, DRM, and broad site coverage remain open. |
| Distribution | No public Galileo Browser build is available. | Not ready | Installation, signing, updates, rollback, and support still need work. |
The goal
Opening pages is only the beginning. A real release also needs reliable standards support, user safety, accessibility, desktop stability, and a maintenance plan.
Support modern standards and make more real websites work reliably.
Build the workflows people expect from a desktop browser.
Test security, privacy, accessibility, stability, installation, and updates.
Keep useful engine work suitable for upstream whenever practical.