Truly independent web browser
Find a file
Jelle Raaijmakers ae21b3a971 LibWeb: Exclude trailing whitespace from line width when placing floats
When generating line boxes, we place floats simultaneously with the
other items on the same line. The CSS text spec requires us to trim the
whitespace at the end of each line, but we only did so after laying out
all the line boxes.

This changes the way we calculate the current line box width for floats
by subtracting the amount of pixels that the current trailing whitespace
is using.

Fixes #4050.
2025-03-26 16:17:29 +00:00
.devcontainer Devcontainer: Set VCPKG_FORCE_SYSTEM_BINARIES when building cache 2025-02-18 15:33:51 -07:00
.github CI: Make JS Benchmarks use the JS repl from the job with the same commit 2025-03-26 11:22:54 +00:00
AK AK: Inline most StringBase member functions 2025-03-26 12:04:00 +00:00
Base/res LibWeb+LibWebView+WebContent: Introduce a basic about:settings page 2025-03-22 17:27:45 +01:00
Documentation LibWeb: Implement functional pseudo-element parsing 2025-03-25 07:54:13 +00:00
Libraries LibWeb: Exclude trailing whitespace from line width when placing floats 2025-03-26 16:17:29 +00:00
Meta Meta: Increase max open file descriptors in WPT.sh 2025-03-25 16:24:06 -04:00
Services LibJS: Replace PropertyKey(char[]) with PropertyKey(FlyString) 2025-03-24 22:27:17 +00:00
Tests LibWeb: Exclude trailing whitespace from line width when placing floats 2025-03-26 16:17:29 +00:00
Toolchain Everywhere: Remove Nix build support 2025-03-24 17:22:08 +00:00
UI UI: Add Cmd+U as a shortcut for "View Source" to AppKit 2025-03-25 17:08:42 -04:00
Utilities LibJS: Use FlyString in PropertyKey instead of DeprecatedFlyString 2025-03-24 22:27:17 +00:00
.clang-format
.clang-tidy Meta: Disable clang-tidy “implicit-bool-conversion” check 2025-01-24 09:25:37 +01:00
.clangd
.editorconfig
.gitattributes
.gitignore Everywhere: Hoist the Libraries folder to the top-level 2024-11-10 12:50:45 +01:00
.gn
.mailmap
.pre-commit-config.yaml
.prettierignore Everywhere: Hoist the Libraries folder to the top-level 2024-11-10 12:50:45 +01:00
.prettierrc
.swift-format
.ycm_extra_conf.py
CMakeLists.txt Meta: Link with OpenSSL explicitly 2025-02-17 12:36:26 +01:00
CMakePresets.json CMake: Ensure build and test presets for Distribution and Debug 2025-02-21 12:05:18 +01:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md Meta: Switch to clang-format-19 as the standard formatter 2024-12-28 05:39:32 -08:00
ISSUES.md Docs: Add info about --enable-idl-tracing flag 2025-01-15 13:25:35 +00:00
LICENSE Meta: Update license year 2025-02-10 11:40:57 +00:00
README.md Libraries: Remove LibArchive 2024-11-25 13:37:45 +01:00
SECURITY.md
vcpkg-configuration.json
vcpkg.json Meta: Add explicit vcpkg dependency for zlib 2025-03-19 13:46:50 +01:00

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.