Best viewed in Nordstjernen

Nordstjernen is an independent, unique web browser

This month for the Nordstjernen web browser

A review of the last 30 days — 11 June to 11 July 2026. Ten point releases, the last absent rows in the HTML standard closed, and a hard push on real-world video, content blocking, on-device safety and platform reach — all while staying no-JIT and telemetry-free.

Nordstjernen (“the North Star”) is a web browser written from scratch in C, built in Norway — a clean-room engine small enough for one person to read end to end. This is what changed in the last month. If you only read one line: the engine grew from roughly 109,000 to about 145,000 lines of C, shipped ten releases (1.0.8 → 1.0.18), and reached zero absent rows in the in-scope HTML standard — every §1–§16 element and API is now implemented, partial, or a deliberate non-goal.

« Back to nordstjernen.org

Nordstjernen rendering a web page
Nordstjernen’s about:start page, redesigned this month. more screenshots »

The month by the numbers

10 releases — 1.0.8 through 1.0.18, shipped between 15 June and 6 July, with 1.0.19 now in development on main. Roughly a thousand commits landed in the window.
~109k → ~145k lines of C — the clean-room engine grew by about a third and is still small enough to audit end to end. No JIT; W^X holds process-wide.
140 / 31 / 0 — the section-by-section walk-through of the HTML standard (§1–§16) now records 140 rows fully implemented, 31 partial, and 0 absent, up from 123 / 48 / 4 at the start of the month.
+1 platform, −1 platform — a new iOS port that builds end to end in CI arrived; OpenBSD was retired. Android is now published on the Google Play Store.

Closing the last gaps in the HTML standard

Nordstjernen measures itself against the spec text, section by section, rather than against another browser. This month the running scoreboard crossed a symbolic line: no element or API row in §1–§16 is fully absent any more. Everything is implemented, tracked as partial, or a by-design non-goal (plugins, frame/frameset, applet/marquee, telemetry, and AI-style web APIs). The remaining work is now refinement of partial rows — multi-column vertical text, iframe srcdoc, quirks-mode deltas — not blank spaces.

JavaScript conformance got the same treatment: several deep passes against the test262 suite drove the unexpected-failure count down (one pass went from 28 to 15), alongside a stream of spec-accuracy fixes to DOM nodes, CSSOM serialization, forms, fetch, encodings, history and messaging. A serve-free local web-platform-tests runner (wpt-local.sh) was added so conformance can be checked without standing up a server.

Real-world video, done the small way

The largest single theme of the month was making inline video work on real sites — without importing a media stack. The pieces came together across several releases:

Underneath all of this, the audio path was rebuilt (1.0.10): SDL2 output with in-tree pl_mpeg (MP2) and minimp3 (MP3) decoding replaced the previous vendored backend, keeping audio as a handful of single-file decoders in a separate unsandboxed helper rather than a codec library in the renderer. Capture arrived too — camera and microphone via getUserMedia, each behind a per-site permission prompt.

Content blocking and on-device safety

Release 1.0.16 added two privacy-and-safety features that run entirely on your machine:

Networking, modernised

More of the web platform

Beyond media, a batch of platform APIs and CSS features arrived:

A browser-wide security hardening pass

In keeping with the “small enough to audit” ethos, an end-to-end source review in early July produced dozens of hardening fixes at once. Among them:

Platform reach

Shell and UI polish

Scope discipline: the email experiment

Not everything that was tried stuck — and that is by design. Around 1.0.17 an experimental built-in email client (about:email, IMAP/POP3/SMTP with provider auto-configuration, primary-password-encrypted credentials and attachment viewing) was added, and then removed a few days later to keep the browser focused on being a browser. The project’s guiding principle is to cut scope rather than corners; the email client is a clean example of that in action.

Release timeline

1.0.8 · 15 JunStability; CSS cursor keywords with platform fallback chains.
1.0.9 · 16 JunEngine and documentation maintenance; OpenBSD retired as a build target.
1.0.10 · 18 JunAudio overhaul (SDL2 + pl_mpeg + minimp3); security hardening.
1.0.11 · 19 JunImport maps for ES modules; WebGL getShaderPrecisionFormat (three.js renders); layout fixes.
1.0.12 · 21 JunHTTP/2 connection multiplexing; a tabbed Developer Tools console window.
1.0.14 · 23 JunInline WebM (VP9/VP8 + Opus/Vorbis); CSSOM rule model; HTMLImageElement.decode(); the WebVTT text-track model.
1.0.15 · 25 JunMaintenance; a QuickJS interpreter fast path for object/string equality.
1.0.16 · 27 JunInitial WebExtensions with declarativeNetRequest content blocking; local Safe Browsing; updated vendored engines.
1.0.17 · 30 JunReplaced-element sizing per spec; camera + microphone capture; a dedicated AI Window; more test262 fixes.
1.0.18 · 6 JulThe media + hardening release: out-of-process video helper across desktop platforms, the source-review security pass, a signed/notarised macOS build, WebGL on by default.
1.0.19-dev · on mainiOS builds in CI; Navigation API; customized built-in elements; vertical writing-mode; native open-media decoders; WebVTT captions over inline video; Android 14 support.

What stayed the same

Through all of it, the constraints held. Nordstjernen still ships no JIT (the renderer never needs writable-executable memory), no telemetry, and no auto-update pinger. Each tab’s engine still runs in its own sandboxed process behind an IPC and shared-memory boundary, seccomp- and Landlock-confined on Linux. The whole engine is still clean-room C, still vendored in-tree with no submodules, and still small enough for one person to hold in their head. A busy month — measured against a fixed North Star.

« Back to nordstjernen.org · full commit history »