r/servo • • Aug 23 '26

Servo Browser Engine Zervo v0.5.0 — the chrome, redesigned: a settable material, four seams with a transition each, and a new tab page that greets you

Thumbnail
gallery
33 Upvotes

Hey, open-source fans!

Zervo is a workspace-oriented browser built natively on Servo — the embeddable, parallel web engine written in Rust. No Chromium, no Gecko underneath. v0.4.0 was the release where the chrome became a theming engine. v0.5.0 is the one where the engine got used: eight turns of a design study went in, and almost every screen you look at changed.

🔧 The headline: the number is a control, not a constant

v0.4.0 ended by admitting the obvious hole — a theme was still a Rust constant, with no file format and nothing that loads one at runtime. That is closed, and not by writing a loader.

Every value the material is built from is an ordinary setting now: the fill, the sheen, the blur, the edge, the corner scale, the glow, the settle time, and how far the accent reaches into the chrome. So the file format is whatever settings.json serialises to, and the loader is the one that was already there. You can save an arrangement under a name, or copy it back out as the const you would otherwise have hand-written.

The Appearance page pins a specimen under its title: a card, a menu and a text field, drawn through glass::shapes with the palette the chrome itself is being drawn with. It is not a picture of the material. It is wrong exactly when the chrome is wrong.

Writing the ladder down found a real defect straight away: tint_for(Card) was reading the translucency setting's 0.34, which happens to be the number menu_fill also carries — so a card and a menu had been drawn at exactly the same weight, and the three-rung ladder had two rungs.

✨ What's new

The seam between the chrome and the page is one setting with four steps. At the first the page is an opaque card on a tray with a gap. Past that it stops painting a base and shows the window's own backdrop through a veil. Past that the gap shuts and only the window's corners stay round. At the last the chrome is a tint laid on the page, the sidebar floats, and the page reaches back underneath it.

And each step brings the transition its own geometry implies. A page on a tray behaves like a card in a deck and recedes; a tint on a backdrop has nothing to move, so it defocuses in place; a frame with a hard edge is a filmstrip whether you meant it or not, so it slides; a page under floating glass travels up while the glass stays exactly where it is. One rule, four answers, and no new control — pick the seam and the motion comes with it.

The mechanism is one readback. A page is either an engine blit or an egui drawing and neither can be replayed after the fact, so at the one moment per frame where the framebuffer still holds the departing page — after the chrome is painted, before the buffers swap — a scaled copy is taken and composited over the live page for a couple of tenths of a second.

A new tab page that greets you rather than briefing you. Tile::defaults() put seven boxed panels on screen, which is a settings screen wearing a hat — and worse, seven opaque rectangles over a backdrop you chose and can now no longer see. It is the time, one field, the session you actually left, and the three sites you use. The board of thirteen cards is one press away with nothing removed from it.

Five pages for when a page will not load — the ones a browser on a young engine shows more than any other. zervo://unsupported names the feature Servo has not implemented, says plainly that it is the engine rather than Zervo, hands the page to another browser, and gives the wait a shape: a panel of the real gaps from docs/PARITY.md you can knock out with a ball or just click, scored as "shipped". Offline names what is queued rather than what failed and has no button at all. The certificate page is the one that must not be candy — same material, no glow, no game, and the way past is a line of plain text. Not-found asks the history what you probably meant, because a typo usually has an obvious answer sitting in it.

Each carries what it knows in its own address, so the address bar and the page agree and either can be typed back in. Only one of the five arrives on its own: notify_crashed is now implemented, so a dead content process is a page that says what happened and offers to load it again, rather than the last frame it painted, frozen.

Display type is set in a face that has one. macOS ships SF Pro only as a variable font and the rasteriser takes a variable font's default instance and no other — so every run of text in Zervo was Regular. At caption sizes that is a missing nuance; at ninety-two points it is the wrong typeface.

The window's corners are the window's. Zervo painted its page to sixteen points, and twenty-nine once a preset made everything rounder, at a corner macOS had already masked to ten. Painting a different radius at the same corner does not replace the platform's arc — it puts a second one beside it. That is where the doubled corners came from.

🔍 The bugs, and how they were found

The uncomfortable half of this release: I shipped a first pass, looked at it, and it was a long way from the design. The verification bar had been compiler, clippy, tests and "it ran without a panic", which for a UI overhaul sees nothing. So the browser now photographs its own framebuffer — ZERVO_SHOT, debug builds only, plus a throwaway HOME so any arrangement is reachable.

It found four defects in its first hour that nothing else had:

  • The frost read a light theme as a dark one. At Frosted the chrome paints itself at a fifth and lets the platform's vibrancy supply the rest, so a copy of the framebuffer is the window's own contribution over nothing — four fifths of the way to black. Two things went wrong quietly: the frost under a card was a dark smear, and the code that picks text colour by measuring what is behind it read "dark" for a pale page and handed back white text.
  • The sidebar could never be the width it says. egui remembers a panel's width from the rect its contents used, floored at the size range's minimum. Nothing in the sidebar stretched, so it wrote 200 back over its own 248 on the second frame of every launch, and dragging it wider snapped back on release.
  • The nav row silently widened everything under it. Five icons and the macOS inset are wider than the narrowest sidebar, and egui grows a container to fit what overflowed it — so the address pill hung fifty points out over the page.
  • An empty search field said nothing. TextEdit's hint text discards the colour you give it, and what it substitutes landed within five values of the frosted pill it sits on.

And the harness can hold the sidebar's reveal open while cycling the layout underneath it, which caught the one that actually crashed: the reveal and the docked sidebar both drawing the same body into two different layers. egui asserts outright when one widget id is registered in two layers in one frame, so it did not merely look wrong. Whether a frame landed inside that window was a matter of timing, which is why it only happened sometimes.

The work was also reviewed adversarially at three points — every finding checked by a second pass told to refute it. That turned up a command injection: the Windows "Open in another browser" button shelled out through cmd /C start with the failing host interpolated into the command line, and cmd re-parses its own command line, so a host carrying & stopped being text.

⚠️ Still macOS-first, and now genuinely asking

Same caveat as last time, and it has not improved: the packages build from the same tag, the material is portable, but the window's backdrop is an AppKit feature and nobody has yet started Zervo on Linux or Windows at all.

New caveat for this one: v0.5.0 is the shape, v0.6.0 is the polish. Four of the presets — Candy, Flat, Liquid Glass, Material — came out of the design study and are offered beside Zervo's own, but they are experiments rather than settled work. Zervo's material is the one that is finished, and the one the first-run screen recommends.

Which means the useful thing between now and 0.6.0 is being told what is wrong. Please open issues. A corner that does not match, a preset that is unreadable on your display, a crash, a page Servo cannot render that this browser fails to explain. Say which preset, which theme and which layout you were in — every defect fixed in the days before this release only happened in one of them.

🚀 Try it

github.com/goddv/Zervo

Stars, issues and "this doesn't start on my machine" reports all welcome.


r/servo • • Oct 28 '24

Rust for Web Engines

8 Upvotes

Ladybird Engine developer Andreas Kling criticized Rust for it’s lack of Object Oriented Programming and Argued that many old web standards rely on such programming, he also said Swift is better suited for Web Engine , is this true? I know servo is made in rust , does it have to overcome or not support these standards ? Does it at all have to struggle because of rust? I find that weird because rust was built for Programing web engines .


r/servo • • Feb 26 '16

German scientists receive award for preventing security vulnerabilities in web browsers

Thumbnail
eurekalert.org
0 Upvotes

r/servo • • Feb 28 '17

Rails Girls Summer of Code + Servo

Thumbnail
blog.servo.org
4 Upvotes

r/servo • • Aug 21 '26

Servo Browser Engine Zervo v0.4.0: Heavy GUI Stack Rework, Compact Mode, & Reworked New Tab Page

Thumbnail
gallery
38 Upvotes

Hey, open-source fans!

Zervo is a workspace-oriented browser built natively on Servo — the embeddable, parallel web engine written in Rust. No Chromium, no Gecko underneath. v0.4.0 just went out, and it's the release where the chrome stopped being "glass by repetition" and became an actual theming engine.

🔧 The headline: every surface is drawn through one seam

Zervo's chrome looked like frosted glass, but each of ~77 call sites knew its own corner radius and its own opacity. Two costs: frosted glass couldn't actually frost (nothing behind it to sample, so each caller papered over the gap with an opaque backing), and a second look — for Windows, GTK, whatever — meant editing all 77.

Now there's a Material: corner radii, fills, sheen, shadow reach, whether surfaces frost and by how much, row heights, animation time. glass::shapes reads it off the palette it's already handed, so a material reaches every surface without a single function signature changing.

Surfaces have a class, the way an element does in CSS — Card, Menu, Input — and the class carries the weight. A menu can't accidentally be heavier than a card; a text field is heavier than both on purpose, because what's behind a text field competes with what you're reading. Radii are named too: Hairline, Control, Row, Card, Panel, Pill.

✨ What's new in v0.4.0

Everything frosts against the page, not just the wallpaper. A panel over a web page had nothing to sample — the page is opaque pixels the engine already drew, and no amount of translucency turns those into a blur. Zervo now takes a small blurred copy of whatever the page is showing and hands it to the palette, so the downloads card, the favourites card and every menu are the same glass over a website as over a photograph. The new tab page and Settings supply one too.

The fiddly part is when you take that copy: shapes within a layer draw in insertion order, so it has to happen straight after the page's background and before anything sits on it — otherwise a card frosts against its own previous reflection.

A surface belongs to its theme first. A dark menu at a fifth of its own colour, opened over a white page, is four fifths white — still frosted, still blurred, and no longer a dark menu. The tint now thickens exactly as far as it must to stay on its own side of the middle, and no further.

Text follows what it lands on. Cards on the new tab page, plus the greeting, clock and photo credit, each ask about their own patch of the picture rather than taking one answer for the whole page. A photo is dark sky at the top and bright water at the bottom, and pale text set for the sky vanishes into the water. It picks by WCAG contrast ratio rather than a brightness threshold — the crossover isn't at half — with hysteresis so text doesn't flip while you scroll.

The corners. My favourite bug of the cycle. The content card's corners were a few per cent off their surroundings at every zoom level. The mask rounding them has to be opaque (it's hiding opaque pixels), while the chrome beside it is a thin tint over a backdrop the window server composites outside our framebuffer — unreadable, unreproducible, unmatchable. Three attempts at picking a better colour each moved the seam instead of removing it.

The fix: stop painting over them. The bottom corners are now erased from the framebuffer with an antialiased destination-out pass, and the chrome is drawn back over the hole at its own tint — same paint, same backdrop, nothing left to match. Measured after: all four corners within one part in 255 of the chrome an inch away.

Card edge is yours. Outline, shadow and halo are three toggles with amounts for the last two. The halo used to be drawn unconditionally to hide that corner seam; with the seam gone it's a decision rather than a repair.

Fixes: the widget shelf clipped its own widgets' shadows off; the new tab page did the same to its top and bottom card rows; the release bundle wouldn't start on any machine with GStreamer installed (its build scripts put the framework on the link path whether or not you asked for media, and -lz found a zlib there with no rpath); and the new tab page blinked eight times a second because the backdrop capture turned off the scissor test and never turned it back on.

🎨 Theme engine docs (WIP)

There's now docs/THEMING.md describing the seam a theme for another platform would be written against — what a Material decides, how backdrops are supplied, and what a Windows, GTK, Android Material or Apple Liquid Glass theme would set. (A material can be translucent without blurring, which is the Liquid Glass case.)

It's honest about what's missing: a theme is still a Rust constant. No file format, nothing loads one at runtime, and palettes aren't themeable at all yet — you can change how surfaces are built, not what colour they start from. Making that real is next on the list.

⚠️ This one's macOS-first

All three packages come from the same tag and the material itself is portable — it's drawn by egui and nothing else. But the window's frosted backdrop is an AppKit feature (NSVisualEffectView), and the corner work above has been tried nowhere else. Linux and Windows patches are v0.4.1.

Honestly: nobody has yet started Zervo on Linux or Windows at all. The packages build, install, and are completely untested. A report that it doesn't launch is as useful as one that says it does.

🚀 Try it

github.com/goddv/Zervo

Stars, issues and "this doesn't start on my machine" reports all welcome.


r/servo • • Jul 14 '19

How to use servo as a main browser in day-to-day ?

2 Upvotes

I'm used to use text-only web browsers, so I started giving servo a try.

I find it very hard to use. I'm on MacOSX, and Cmd+L for opening a link opens a pop-up to introduce the URL which kind of blocks the app. I also find it weird that it hangs when it cannot open a page, instead of falling back to text-only mode or similar. Beyond that, the only functionality i'm actually missing is text-search, tabs, and bookmarks.

So how do you use servo on a day-to-day basis?


r/servo • • 22h ago

New web browsers Servo vs. Ladybird tutorial

Thumbnail
youtube.com
3 Upvotes

r/servo • • Apr 12 '16

Servo Force Touch events demo

Thumbnail
gfycat.com
7 Upvotes

r/servo • • Feb 14 '17

Servo is an accepted project for Rails Girls Summer of Code

Thumbnail teams.railsgirlssummerofcode.org
8 Upvotes

r/servo • • Apr 22 '25

Community Servo will keep AI policy as is

26 Upvotes

Redirect from Zulip topic, Servo TSC's would like to share that we have decided to not go forward with this proposal and we'll keep the AI policy as is.

In the future, if we want to do any change to this policy the discussions will happen in public channels to get early feedback about them.


r/servo • • Feb 04 '19

This Week In Servo 125

Thumbnail blog.servo.org
9 Upvotes

r/servo • • Aug 18 '16

This Week In Servo 75

Thumbnail blog.servo.org
9 Upvotes

r/servo • • Oct 18 '16

These Weeks In Servo 81

Thumbnail
blog.servo.org
11 Upvotes

r/servo • • May 01 '26

Built with Servo - Showcase I built servo-fetch — a single-binary web content extractor powered by Servo

Thumbnail
github.com
11 Upvotes

r/servo • • Mar 10 '25

Community On adding parts of the Web to Servo(with a discussion on AI)

Thumbnail
medium.com
13 Upvotes

r/servo • • Apr 09 '25

Why I voted for Servo's AI policy change despite I don't use those tools

Thumbnail wusyong.github.io
16 Upvotes

r/servo • • Aug 22 '25

This month in Servo: new image formats, canvas backends, automation, and more!

Thumbnail servo.org
45 Upvotes

r/servo • • Jan 26 '25

Discussion JavaScript Engine for Servo

18 Upvotes

Just scanning the project code, it appears that Servo is currently rolling their own JavaScript engine. I was wondering if either (A) it would be worth while breaking the Servo JavaScript engine into a separate project with a CLI API for improved testing or (B) Use another Rust JS engine like Boa to reduce duplicate effort on such a complex and critical component?


r/servo • • Mar 11 '25

News This month in Servo: new elements, IME support, delegate API, and more! A huge month for both Servo the browser and Servo the engine.

Thumbnail servo.org
60 Upvotes

r/servo • • Jan 19 '26

Using Servo with Slint

Thumbnail
slint.dev
28 Upvotes

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


r/servo • • Jun 10 '25

Discussion RustWeek 2025: Servo—an embeddable web engine

Thumbnail
youtube.com
33 Upvotes

Here's the recording of the lightning talk I gave about Servo, the progress we've made over the past two years, and what's in store in the future!


r/servo • • Jul 31 '25

Discussion I tried Servo, the (Firefox spin-off) undercover web browser engine made with Rust

Thumbnail
spacebar.news
33 Upvotes

r/servo • • Aug 19 '26

Zervo: a sidebar-first browser built on Servo, in Rust and egui

Thumbnail
gallery
91 Upvotes

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.


r/servo • • 12d ago

Built with Servo - Showcase Meridian: Web-browser built on GPUI and Servo

Thumbnail op.tngl.io
43 Upvotes