LadybirdBrowser /

Ladybird

Live map
View repository
Snapshotmaster · 368d541

Independent browser processes fetch resources, build web-platform state, execute JavaScript, lay out content, and composite it.

Click a building or route
Choose a path

Load a URL and turn its document into a visible frame.

System map8 components · 9 connections
130%
Ladybird: a page becomes pixels architectureBegin at the browser UI, cross into WebContent, then move from loading and DOM through style, layout, paint, and composition.URL and navigation opt…request and page contextbytes, MIME type, and …elements, stylesheets,…computed CSS and contentbox geometry and visua…composited surfaceResourceloaderBrowser UIWebContentserviceDOM documentStyle computerLayout treeLibJS VMPaint &compositor
Connections
BuildingsEntryServiceComputeStorageRuntimeToolingExternal

Terms, in plain English

WebContentThe isolated service process that owns and executes a web page.

How to study this repo

  1. 1
    Cross the process boundary

    Follow a navigation command from the UI client to PageHost.

  2. 2
    Build a rendering tree

    Connect DOM state to computed style and layout geometry.

  3. 3
    Trigger a repaint

    Trace a script mutation back through invalidation and painting.