Tagged articles
Browser architecture
10 articles · Page 1 of 1
The article analyzes the three emerging AI‑browser architectures—traditional kernel with sidebar, research/agent browsers, and AI‑native browsers—using Tabbit 1.0’s evolution, performance metrics, and product comparisons to assess how deeper AI integration reshapes agent capabilities and the industry's direction.
AI browsersBrowser architectureTabbit
0 likes · 7 min read

This article walks through the complete lifecycle of a web page in modern browsers, covering network fetching, HTML/CSS parsing, layout calculation, painting and GPU compositing, the V8 JavaScript engine pipeline, module loading, multi‑process isolation, and key differences among Chromium, Gecko and WebKit implementations.
Browser architectureChromiumJavaScript engine
0 likes · 47 min read

Chromium evolved from a single‑process browser to a service‑oriented, multi‑process architecture—separating Browser, Renderer, GPU, Network, Storage, and other services into isolated processes and threads—to improve stability, performance, and security while allowing configurable trade‑offs for memory‑constrained devices such as Android WebView.
Browser architectureChromiumWebView
0 likes · 11 min read

Chrome separates browsing tasks into distinct browser, renderer, plugin, and GPU processes, parses HTML/CSS into DOM, layout, paint, and compositing trees, rasterizes tiles on a compositing thread, and uses the GPU process to display frames, enabling optimized, smooth animations such as danmaku while balancing memory usage and security.
Browser architectureChromeFrontend Development
0 likes · 14 min read

The article explains how Firefox redesigned its accessibility engine—moving from a complex, multi‑process architecture to an asynchronous, cache‑driven model—to dramatically speed up screen‑reader interactions, cut thousands of lines of code, and roll out the improvements across Windows and Linux browsers.
Browser architectureFirefoxFrontend Development
0 likes · 6 min read

The QianNiu client migrated its custom Application Embedded Framework to Chromium Embedded Framework, introducing a multi‑process architecture with isolated browser and render processes, remote RPC components, unified JS injection, render‑group optimization, comprehensive network interception, white‑screen detection, and plans for memory reclamation and further security hardening.
AEFBrowser architectureCEF
0 likes · 12 min read

This article explains the internal multi‑process structure of Chrome, covering CPU/GPU basics, browser and renderer processes, the benefits of process isolation, the step‑by‑step navigation flow, how the renderer parses, styles, layouts and composites pages, and how user input events are handled to keep interactions smooth.
Browser architectureChromeProcess Model
0 likes · 23 min read

This article provides a comprehensive, step‑by‑step exploration of modern browsers—covering Chrome’s multi‑process architecture, the navigation pipeline from URL entry to page load, the rendering stages (HTML parsing, style calculation, layout, painting, compositing), and how user interactions are processed and optimized.
Browser architectureFrontend DevelopmentWeb Performance
0 likes · 23 min read

This multi‑part article explains Chrome’s low‑level architecture—from CPU/GPU fundamentals and its multi‑process model to the step‑by‑step navigation flow, the rendering pipeline, and how the compositor processes input events—providing developers with a deep understanding of browser performance and best‑practice optimizations.
Browser architectureChromemulti-process
0 likes · 36 min read

This article systematically explains how browsers use multiple processes and threads, how the rendering pipeline works, why JavaScript runs on a single thread, and how the event loop, macrotasks, microtasks, timers, and Web Workers interact to affect performance and stability.
Browser architectureWeb Workersevent-loop
0 likes · 27 min read
