Truly independent web browser
Find a file
Timothy Flynn 68947d55d9 LibIPC: Do not require constructing containers when sending IPC messages
For example, consider the following IPC message:

    do_something(u64 page_id, String string, Vector<Data> data) =|

We would previously generate the following C++ method to encode/transfer
this message:

    void do_something(u64 page_id, String string, Vector<Data> data);

This required the caller to either have to copy the non-trivial types or
`move` them in. In some places, this meant we had to construct temporary
vectors just to send an IPC.

This isn't necessary because we weren't holding onto these parameters
anyways. We would construct an IPC::Message subclass with them (which
does require owning types), but then immediate encode the message to
an IPC::MessageBuffer and send it.

We now generate code such that we don't need to construct a Message. We
can simply encode the parameters directly without needing ownership.
This allows us to take view-types to IPC parameters.

So the above example now becomes:

    void do_something(u64, StringView, ReadonlySpan<Data>);
2025-03-09 11:14:20 -04:00
.devcontainer Devcontainer: Set VCPKG_FORCE_SYSTEM_BINARIES when building cache 2025-02-18 15:33:51 -07:00
.github CI: Bump JamesIves/github-pages-deploy-action from 4.7.2 to 4.7.3 2025-02-25 08:42:16 +01:00
AK LibWeb: Add opt-in tracing of update_layout() calls with reason 2025-03-08 03:37:38 +01:00
Base/res Inspector: Keep property filter across tabs 2025-02-17 12:55:30 +01:00
Documentation Documentation: Describe how to sniff the DevTools protocol with Firefox 2025-03-04 15:42:39 -05:00
Libraries LibIPC: Do not require constructing containers when sending IPC messages 2025-03-09 11:14:20 -04:00
Meta LibIPC: Do not require constructing containers when sending IPC messages 2025-03-09 11:14:20 -04:00
Services LibIPC: Do not require constructing containers when sending IPC messages 2025-03-09 11:14:20 -04:00
Tests LibWeb: Implement the HTMLInputElement.list attribute 2025-03-09 15:10:55 +00:00
Toolchain Nix: Expose ladybird package in flake; reuse in shell 2025-03-04 08:19:54 -07:00
UI LibIPC: Do not require constructing containers when sending IPC messages 2025-03-09 11:14:20 -04:00
Utilities LibDNS: Ensure non-blocking socket is used for TCP connections 2025-02-22 18:39:58 +01:00
.clang-format Meta: Support using clang-format on Objective-C++ files 2023-08-22 21:36:19 -04:00
.clang-tidy Meta: Disable clang-tidy “implicit-bool-conversion” check 2025-01-24 09:25:37 +01:00
.clangd Meta: Change the default build directories to exclude "ladybird" prefix 2024-11-06 10:38:57 -07:00
.editorconfig Meta: Add .editorconfig 2022-09-10 17:32:55 +01:00
.gitattributes LibGfx: Remove support for the various "portable" image formats 2024-06-17 21:57:35 +02:00
.gitignore Everywhere: Hoist the Libraries folder to the top-level 2024-11-10 12:50:45 +01:00
.gn Meta: Automatically generate a compilation database for clangd 2023-11-14 14:29:35 -05:00
.mailmap Meta: Update my e-mail address everywhere 2024-10-04 13:19:50 +02:00
.pre-commit-config.yaml Meta: Replace deprecated pre-commit stage name 2024-10-18 09:40:59 +02:00
.prettierignore Everywhere: Hoist the Libraries folder to the top-level 2024-11-10 12:50:45 +01:00
.prettierrc
.swift-format Meta: Add swift-format configuration 2024-07-30 18:38:02 -06:00
.ycm_extra_conf.py Meta: Make YCM return flags as Python list 2024-07-06 14:50:43 -06:00
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 Meta: Add code of conduct (from the Ruby community) 2024-10-02 09:49:52 +02:00
CONTRIBUTING.md Meta: Switch to clang-format-19 as the standard formatter 2024-12-28 05:39:32 -08:00
flake.lock Nix: Remove flake-utils from inputs 2025-03-04 08:19:54 -07:00
flake.nix Nix: Expose ladybird package in flake; reuse in shell 2025-03-04 08:19:54 -07: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 Documentation: Make updates to align better with new issue template 2024-10-31 09:18:08 +01:00
shell.nix Nix: Fix OpenGL linking issue in the devshell 2025-02-05 13:41:45 -07:00
vcpkg-configuration.json Meta: Add overlay port for vulkan-loader 2024-07-07 15:56:59 +02:00
vcpkg.json vcpkg: Explicitly use OpenSSL backend with curl 2025-02-28 14:28:29 -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.