Loading...
Loading...
Ladybird’s April 2026 progress report highlights accelerating work on a truly independent, non‑Chromium browser engine—alongside the ecosystem frictions such projects face. The project merged 333 PRs, added notable sponsorship (including a $50,000 Human Rights Foundation grant), and shipped user-facing features like an inline PDF viewer powered by pdf.js plus a richer, SQLite-backed history and autocomplete. Under the hood, incremental/speculative HTML parsing and off-thread JS bytecode compilation aim to cut latency and improve responsiveness, while per-iframe rasterization boosts parallelism. Meanwhile, Firefox users surfaced similar “hidden capability” dynamics with a UI extension enabling Brave’s adblock-rust engine, underscoring demand for more configurable, competitive browser tooling.
Ladybird’s April 2026 update merged 333 PRs from 35 contributors and added two new sponsors, including a $50,000 grant from the Human Rights Foundation. Key product changes: an inline PDF viewer powered by pdf.js; a SQLite-backed browsing HistoryStore with rich, favicon-aware address-bar autocomplete and a Clear History setting; incremental and speculative HTML parsing that streams bytes into the tokenizer and prefetches resources to avoid duplicate requests; off-thread JavaScript bytecode compilation that shifts ~200ms of main-thread work to background threads; per-navigable rasterization so iframes rasterize on separate threads, paving the way for sandboxed iframe processes; and JavaScript engine optimizations improving JS-to-JS and native call paths after a C++/Rust transition. These changes boost performance, parallelism, and web-compatibility.
The Ladybird browser project published its April 2026 update, showing steady progress toward a usable non‑Chromium browser. Key developments include bug fixes (notably improving CSS Doom compatibility), ongoing build and packaging work, and plans for an alpha prebuilt binary in June. The Hacker News discussion highlights broader ecosystem hurdles: site-level Chromium favoritism, Widevine DRM access challenges, and user‑agent compatibility issues that have forced other browsers to mimic Chrome. That context matters because browser diversity affects web standards, user choice, and competition; Ladybird’s progress tests how a smaller, independent engine can handle real‑world compatibility and DRM gatekeeping from major platforms. The update signals momentum but underscores practical barriers ahead.
Ladybird merged 333 PRs in April, added new sponsors including the Human Rights Foundation, and shipped several performance and feature upgrades to the open-source browser. Key user-facing features include an inline PDF viewer via pdf.js and a rich, SQLite-backed browsing history with autocomplete and privacy controls. Under the hood, the project implemented incremental and speculative HTML parsing to stream and prefetch resources, off-thread JavaScript bytecode compilation to cut main-thread time (e.g., ~200ms savings on YouTube), per-navigable rasterization so iframes rasterize on separate threads, and multiple JavaScript engine optimizations after a C++/Rust transition to speed JS-to-JS and native calls. These changes improve load latency, parallelism, and responsiveness, and lay groundwork for sandboxed iframe processes.
Ladybird’s April 2026 update shipped 333 merged PRs from 35 contributors and added new sponsors, including a $50,000 grant from the Human Rights Foundation. Key product advances include an inline PDF viewer powered by pdf.js, a SQLite-backed history store that powers a rich address bar autocomplete with favicons and visit metadata, and incremental plus speculative HTML parsing to start resource discovery before full body download. Performance work moved JavaScript bytecode generation off the main thread, enabled per-navigable rasterization so iframes render independently, and delivered faster JS-to-JS and native call paths in the browser’s JS engine after a C++→Rust transition. These changes improve load latency, parallelism, and responsiveness.
Firefox 149 ships adblock-rust (Brave's Rust engine, MPL-2.0) completely disabled with no UI. It's controlled by two about:config prefs with no WebExtension API, so you can't touch them programmatically from a standard extension.<p>This extension gives it a UI: ETP toggle (via browser.privacy API, instant), filter list manager with clipboard helpers for the manual about:config steps, and 8 preset lists. You can also add your own if you so desire.