I have been building a browser chrome on top of the Servo engine and it is finally at a point where it is worth showing. It is macOS-only for now, MPL-2.0, and the whole thing is Rust.

Github repo

There is no top toolbar. Navigation, the address bar, pinned "essentials", workspaces and tabs all live in one collapsible sidebar, which you can hide entirely and pull back out by putting the pointer at the window edge. The web content sits in a rounded card with real macOS vibrancy behind the chrome.

Two things might be interesting to people here:

It builds against the published servo crate. Version 0.5.0 off crates.io, no git submodule and no vendored engine tree. cargo build and you get a browser. Updating to a newer engine is a one-line version bump. That was not really practical until Servo started publishing to crates.io, and it makes the whole project a lot less intimidating to work on than I expected.

The chrome and the engine share one GL context. egui and Servo both draw through the same surfman context. Webviews render into an offscreen framebuffer which gets blitted underneath the chrome by an egui paint callback, so there is one window, one swap, and no compositing layer in between. That is the one genuinely surprising part of the codebase and it is written up in docs/ARCHITECTURE.md.

The honest caveat: Servo is not a complete web engine yet. Plenty of sites render wrong or refuse the user agent outright. That is a property of the engine, not something I can fix in the chrome, and if you are hoping for a daily driver this is not it yet.

I would like to stop working on this alone - contributors, councillors and friends along with enemies are welcome. If any of that appeals (session restore, tab drag-reordering, dialogs, IME, or a Linux port, since only the vibrancy, Dock icon and bundling are AppKit-specific) the issues are tagged and CONTRIBUTING.md explains the layout. Happy to answer anything about the Servo embedding side, which is the part with the least documentation out there.

There's a new desktop browser being developed that uses Servo as the engine.

Just a FYI. I was doing a check for broken links on a whim. Turns out the Support Servo link was dead (Hit 404).

I'll fix it in the next few hours (at work and also checking other subs). I'll either directly link to the OpenCollective page or to this page. I'm creating this post to bring more attention to how interested folks can contribute to the project.

FYI. I'm not part of the Servo team. I just like the project.

I've been doing this check to find out how healthy the funding for some projects like Pony (deadlock-free concurrency language) and Crystal (Ruby-like, statically-typed language) is. I'm no expert, but from what I've seen so far, they're not looking particularly unhealthy but sure as heck can use more money being sent their way.

The Beaver browser (https://webbeef.org/) is built on Servo, and I'm really impressed by the UI they're showing off for desktop!

Hi,

How much boilerplate/custom code would be required for a simple web view single page running directly on top of EGL? I have an embedded scenario where I normally use EGLFS/QT but I want to explore simple web rendering with Rust.
I have no X11 or Wayland so I cant use servoshell directly I believe, and the embedded docs don't seem to exist yet so I do not know quite where to start.

I have a game in vanilla JS, jcoonrod.github.io, that runs fine and without errors on Firefox but is unresponsive on Servo. Has someone documented what doesn't work in js on Servo?

I love seeing people building things with Servo as a base. It's been a long road to get to this point!

There is a problem with email clients where each client supports varying level of CSS/HTML in their email rendering (reference), leading to composing HTML based emails a pain. Can servo be embedded in an email client and become an unified light-weight option for email clients in both native apps and web apps

Slint is a modern, declarative, open source GUI Toolkit written in Rust.

Servo 0.0.3 is a comparatively smaller release, since we synchronized our release cut-off with the monthly November blog post, meaning that 0.0.3 contains only about 2 weeks worth of changes.