Web compatibility
Support modern standards and make more real websites work reliably.
Roadmap
What works now—and what comes next.
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.
Development path
Five stages from first build to public alpha.
We are working through the foundation now. Later stages begin only when the earlier work is stable enough to support them.
- 01Current
Foundation & baseline
Make builds repeatable and document the browser we inherited from Servo.
- 02Started
Core browser journeys
Test rendering, navigation, storage, media, and the desktop shell.
- 03Next
Compatibility & hardening
Expand standards, real-site, security, privacy, and accessibility work.
- 04Later
Packaging & updates
Build installation, updates, rollback, recovery, and platform integration.
- 05Goal
Public alpha
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
What we can test today.
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
A browser people can use and trust.
Opening pages is only the beginning. A real release also needs reliable standards support, user safety, accessibility, desktop stability, and a maintenance plan.
Everyday browser features
Build the workflows people expect from a desktop browser.
Safe releases
Test security, privacy, accessibility, stability, installation, and updates.
A healthy Servo relationship
Keep useful engine work suitable for upstream whenever practical.