How browsers work?
summary
Explains the rendering engine end to end: HTML needs an unconventional parser because it is not context free, WebKit uses Flex and bison for lexer/parser parts, and parsing builds a DOM while a simultaneous render tree of rectangles is created. Layout (reflow) uses a dirty‑bit system to avoid full recompute, paint follows background border children outline order, and examples include a site with 1,500 texts that still renders and a toy engine implemented in ~1,000 lines that displays basic pages.
AI-written summary · about
chapters (4)
related talks
27mAnatomy of a Browser
55mHow the Browser Works
41mWebKit Rendering: Overview for HTML5 Developers
44mWe Are All Good with Browsers Made by Others
22mDOM implementation techniques
30mPulling Back the Curtains From Your Stylesheets
27mFrom Parentheses to Perception: How Your Code Becomes Someone Else's Reality
52mBuilding Our Own Browser from Scratch. Part One: HTML