Engine integration
Networking, storage, graphics, media, permissions, and browser APIs have to work as one maintainable system.
The engine
How GalileoEngine fits together.
We start with Servo, keep the engine work close to upstream, and add the pieces needed to build Galileo Browser.
Three layers
Each part has a different job.
Servo is the upstream web engine. GalileoEngine is our engine and integration layer. Galileo Browser is the desktop product built on top.
- 01 / upstream
Servo
The Rust web engine and embedding foundation we build on.
- 02 / engine layer
GalileoEngine
Connects Servo to browser features, compatibility work, and our testing process.
- 03 / desktop product
Galileo Browser
The browser interface and everyday workflows people will use.
GalileoEngine is independent from Servo and is not affiliated with or endorsed by the Servo project.
Our part of the work
Connecting a web engine to a complete browser.
Compatibility testing
Standards tests and repeatable browsing tasks show us what works and where we still have gaps.
Release work
Security, privacy, accessibility, stability, installation, updates, and recovery all need their own testing before release.
ServoGalileoEngine
Working with upstream
Keep the fork useful and maintainable.
When a fix is useful beyond Galileo, we want it to remain suitable for Servo. Staying close to upstream also makes future Servo updates easier to adopt.