Truly independent web browser
Find a file
stasoid 6cf627be8a LibCore: Simplify System::open
_O_OBTAIN_DIR flag makes _open use FILE_FLAG_BACKUP_SEMANTICS in
CreateFile call.

FILE_FLAG_BACKUP_SEMANTICS is required to open directory handles.

For ordinary files FILE_FLAG_BACKUP_SEMANTICS overrides file security
checks when the process has SE_BACKUP_NAME and SE_RESTORE_NAME
privileges, see https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-createfilea
2025-02-05 17:36:11 -07:00
.devcontainer Devcontainer: Add a Fedora 41 devcontainer for use in CI 2024-12-31 13:42:50 -07:00
.github CI: Do not insinuate PRs can be reopened in stalebot's close message 2025-01-16 23:40:19 +01:00
AK AK: Add Error::from_windows_error(void) 2025-02-05 17:36:11 -07:00
Base/res LibWeb/CSS: Implement the color-scheme CSS property 2025-01-08 11:18:13 +00:00
Documentation LibWeb: Update add_libweb_test.py to support Screenshot, Ref, and Layout 2025-01-13 14:25:26 +00:00
Libraries LibCore: Simplify System::open 2025-02-05 17:36:11 -07:00
Meta Meta: Open files with explicit encoding in check-style.py 2025-02-05 17:35:10 -07:00
Services Meta: Disallow links to single-page HTML spec 2025-02-05 16:04:50 -07:00
Tests LibWeb: Check if input is disabled before submit event to form 2025-02-05 14:45:57 -07:00
Toolchain Meta: Update vcpkg to the December 2024 release 2024-12-22 11:33:19 +01:00
UI headless-browser: Allow the -f argument to be used multiple times 2025-02-05 06:58:52 -05:00
Utilities LibURL+LibWeb: Make URL::basic_parse return an Optional<URL> 2025-01-11 10:08:29 -05: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
.gn
.mailmap
.pre-commit-config.yaml
.prettierignore
.prettierrc
.swift-format
.ycm_extra_conf.py
CMakeLists.txt CMake: Add workaround for binutils+patchelf incompatability 2024-12-12 17:22:34 -07:00
CMakePresets.json CMake: Rename our triplets to their canonical names 2024-12-22 15:48:30 -07: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
flake.lock Nix: Update flake inputs 2025-02-05 13:41:45 -07:00
flake.nix Flake: Add and run formatter + Rename devshell 2024-12-18 15:15:42 +00:00
ISSUES.md Docs: Add info about --enable-idl-tracing flag 2025-01-15 13:25:35 +00:00
LICENSE
README.md
SECURITY.md
shell.nix Nix: Fix OpenGL linking issue in the devshell 2025-02-05 13:41:45 -07:00
vcpkg-configuration.json
vcpkg.json Meta+LibUnicode+LibJS: Upgrade to ICU 76.1 2025-01-18 17:56:40 -05: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.