1193409f64
HTMLImageElement's update-the-image-data step 16 queues its state transition and load event dispatch via a 1 ms BatchingDispatcher, so the current request does not become CompletelyAvailable synchronously when the fetch finishes. decode()'s on_finish callback, however, was queuing its resolve task directly on the event loop, bypassing the batch. That race meant decode() could resolve while the image request was still in Unavailable state, so any .then() handler inspecting img.width / img.height (or anything derived from the bitmap) would see zeros. Google Maps hits this on its .9.png road shield icons: after awaiting img.decode() it reads a.width / a.height and calls ctx.getImageData(0, 0, 0, 0), which throws IndexSizeError and aborts the tile rendering pipeline. Route decode()'s on_finish through the same BatchingDispatcher so both are processed in the same batch, with the decode resolution queued after step 16's element task.
Ladybird
Ladybird is a truly independent web browser, using a novel engine based on web standards.
Important
Ladybird is in a pre-alpha state, and only suitable for use by developers
Features
We aim to build a complete, usable browser for the modern web.
Ladybird uses a multi-process architecture with a main UI process, several WebContent renderer processes, an ImageDecoder process, and a RequestServer process.
Image decoding and network connections are done out of process to be more robust against malicious content. Each tab has its own renderer process, which is sandboxed from the rest of the system.
At the moment, many core library support components are inherited from SerenityOS:
- LibWeb: Web rendering engine
- LibJS: JavaScript engine
- LibWasm: WebAssembly implementation
- LibCrypto/LibTLS: Cryptography primitives and Transport Layer Security
- LibHTTP: HTTP/1.1 client
- LibGfx: 2D Graphics Library, Image Decoding and Rendering
- LibUnicode: Unicode and locale support
- LibMedia: Audio and video playback
- LibCore: Event loop, OS abstraction layer
- LibIPC: Inter-process communication
How do I build and run this?
See build instructions for information on how to build Ladybird.
Ladybird runs on Linux, macOS, Windows (with WSL2), and many other *Nixes.
How do I read the documentation?
Code-related documentation can be found in the documentation folder.
Get in touch and participate!
Join our Discord server to participate in development discussion.
Please read Getting started contributing if you plan to contribute to Ladybird for the first time.
Before opening an issue, please see the issue policy and the detailed issue-reporting guidelines.
The full contribution guidelines can be found in CONTRIBUTING.md.
License
Ladybird is licensed under a 2-clause BSD license.