Firefox in WebAssembly Runs a Full Browser Inside Another Browser Tab
The project demonstrates that a full browser engine can be ported to WebAssembly, but practical use remains limited by performance, network relay, and stability issues.
Reporting from 1 source: GIGAZINE.
Puter Labs has released Firefox in WebAssembly, a project that compiles Mozilla Firefox's Gecko rendering engine and SpiderMonkey JavaScript engine to WebAssembly, allowing the browser to run entirely within another browser tab. The development used AI models extensively, with token costs exceeding $25,000 (about 4 million yen). The project is positioned as an experiment exploring WebAssembly limits, not a daily-use product.
The project compiles Firefox's Gecko rendering engine and SpiderMonkey JavaScript engine to WebAssembly using Emscripten. Network connections go through a Wisp relay server, so external sites see the relay's IP address. GPU acceleration via WebGL is provided, and an experimental JIT compiler converts JavaScript to WebAssembly for speed. The developer said Firefox was chosen over Chromium because it has better mechanisms for running in a single process.
AI models including Claude Opus and Claude Fable were used for JIT compiler research and bug investigation, consuming about 30 billion tokens at a cost exceeding $25,000. The source code is available on GitHub and can be built on Linux. Input and scrolling do not work properly on smartphones, so the project is an experiment exploring WebAssembly limits, not a finished product for daily use.
Synthesized by Yomimono from the 1 cited source below, including Japanese-language reporting where cited, then editorially reviewed before publishing.