This article reviews Microsoft’s new open‑source portal, Google’s Chrome URL‑hiding experiment, the YAM cryptocurrency bug that locked millions, and the launch of Bootstrap’s official SVG icon library, highlighting their goals, technologies, and community impact.
Browser caching works by storing copies of web resources in memory, disk, or service‑worker caches and using HTTP headers such as Cache‑Control, Expires, ETag, and Last‑Modified to decide freshness, allowing strong (local) and negotiated (weak) cache stages, while developers can fine‑tune performance with CDN settings, IndexedDB, Service Workers, and HTML5 storage to create optimal, auditable cache strategies.
The article explains how modern browsers manage TCP connections for HTTP requests, covering persistent connections, the limits on concurrent connections per host, the behavior of HTTP/1.1 pipelining, why SSL sessions may be reused, and how HTTP/2 multiplexing improves parallel request handling.
This article explains how Alipay’s MiniProgram development tools were migrated to a browser‑based WebIDE using the Kaitian IDE framework, detailing the architecture, startup optimization, plugin system, real‑world deployments, and future plans for a lighter Playground experience.
This article provides a thorough, step‑by‑step explanation of the entire browser request‑response cycle—including URL parsing, DNS lookup, TCP connection, server handling, response processing, and the detailed rendering pipeline—offering clear insight for developers and interview preparation.
This article explores the origins and purpose of the JavaScript event loop, explains how browsers and Node.js implement it with external and internal queues, compares their differences, and illustrates the concepts through detailed code examples and visual diagrams.
This guide shows how to access Chrome’s experimental flags to enable useful features such as webpage thumbnails, media controls, tab freezing, parallel downloading, and tab grouping, providing the exact flag URLs, configuration steps, and notes on version compatibility.
This article explains the fundamentals of HTTP caching, covering forced and conditional cache strategies, key response headers like Cache-Control, Expires, ETag, and Last-Modified, and demonstrates how browsers decide when to serve cached content versus fetching fresh data.
WebAssembly, officially standardized by W3C in December 2019 as the fourth core web language, offers a secure, portable, high‑performance binary format that runs in browsers, enabling near‑native execution for tasks like audio, video, graphics, 3D, and AI, while introducing features such as threads, shared memory, and direct host object access.
This article explains the fundamentals of browser HTTP caching, detailing request and response structures, the processes of forced and negotiated caching, cache-control directives like Expires and Cache-Control, and how browsers store and retrieve resources from memory and disk caches.
This article explains the step‑by‑step process from entering a URL to page rendering, focusing on TCP connection reuse, HTTP persistent connections, pipelining, HTTP/2 multiplexing, SSL session reuse, and browser limits on simultaneous connections for pages with many images.
This article demonstrates how to leverage WebAssembly and Emscripten to compile C code for high‑performance MD5 hashing and archive (zip/7z) parsing in the browser, covering library selection, memory management, file I/O via WorkerFS, async processing, and integration of C functions with JavaScript.
The article explains how modern browsers manage TCP connections for HTTP requests, covering persistent connections, the number of requests per connection, pipelining limitations in HTTP/1.1, the advantages of HTTP/2 multiplexing, SSL reuse, and browser-imposed limits on concurrent connections per host.
The interview with W3C China General Manager Wu Xiaoqian at Tencent's Front‑End Technology Conference explains the origins, syntax, tooling, and future of WebIDL, showing how this language‑neutral interface description helps developers and browser engineers create consistent, standards‑based Web APIs.
This article breaks down the five essential questions about how modern browsers handle TCP connections, persistent HTTP requests, pipelining, SSL reuse, and per‑host connection limits when downloading dozens of images on a webpage.
This article introduces the Kangax ES compatibility table, showing how to view new ECMAScript features, their support across browsers and Node.js, and explains the table’s layout, version selectors, and color‑coded compatibility indicators for developers seeking up‑to‑date feature information.
The article lists DOM properties and methods—such as element measurements, scrolling APIs, focus calls, getComputedStyle, and various window and document attributes—that cause browsers to synchronously recalculate styles and layout, explains why they are performance bottlenecks, and offers practical mitigation techniques.
The article explains how modern browsers handle TCP connections and HTTP requests—including persistent connections, the limits on simultaneous connections per host, the (disabled) HTTP/1.1 pipelining, SSL reuse, and how HTTP/2 multiplexing improves image loading performance.
This article explains the browser rendering pipeline—from network communication and HTML/CSS parsing to DOM and render tree construction—highlighting common misconceptions, performance bottlenecks, and practical optimization strategies such as DNS reduction, TCP reuse, HTTP/2 features, efficient CSS selectors, and JavaScript loading techniques.
An in‑depth look at how browsers handle TCP connections during page loads, covering persistent connections, request limits per host, HTTP/1.1 pipelining, HTTP/2 multiplexing, and why SSL handshakes may be reused, illustrated with real‑world connection timing screenshots.
This article explains the browser's critical rendering path, detailing how HTML, CSS, and JavaScript are transformed into pixels through DOM construction, CSSOM creation, render tree generation, layout, and painting, and discusses how JavaScript can block and delay these stages.
This article explores how WebAssembly, compiled via Emscripten from C/C++ code, can accelerate file‑scanning tasks in a web‑based email attachment uploader, detailing the compilation pipeline, runtime communication, performance benchmarks against pure JavaScript, and practical optimizations for worker‑based processing.
The article explains step‑by‑step what occurs when a user types a URL, covering DNS resolution, browser caching, HTTP requests and redirects, server processing, HTML generation, resource fetching, compression, and asynchronous AJAX communication, using Facebook as a concrete example.
This article explores the full range of browser console functions—including formatted logging, object inspection, warnings, tables, assertions, counters, timing, tracing, and grouping—to help JavaScript developers debug more efficiently and gain deeper insight into their code.
This article examines why console.log may produce surprising results in different Chrome DevTools states, explains the underlying asynchronous I/O handling, and offers practical debugging advice for developers working with JavaScript in the browser.
This article explains how JavaScript’s single‑threaded model achieves asynchronous behavior through macro‑tasks and micro‑tasks, compares the browser and Node.js event‑loop implementations, and demonstrates the timing differences between setTimeout, setImmediate, and process.nextTick with practical code examples.
This comprehensive guide walks experienced front‑end developers through the browser's multi‑process model, internal threading, rendering pipeline, JavaScript single‑threaded execution, event loop mechanics, Web Workers, and performance‑related concepts like macrotasks, microtasks, and hardware‑accelerated compositing.
This comprehensive guide walks you through browser multi‑process architecture, the relationship between processes and threads, the rendering pipeline, Web Workers, and the intricacies of JavaScript's single‑threaded execution and event‑loop mechanisms, providing a solid knowledge framework for front‑end developers.
This article outlines common geographic, device, browser, and Salesforce org configuration problems that cause slow page loads in Lightning Experience and provides practical mitigation steps such as network latency testing, browser benchmarking, disabling unnecessary plugins, and optimizing Visualforce and Lightning page designs.
This article introduces Play‑with‑Docker, a browser‑based sandbox that lets users instantly create Docker servers, use an integrated SSH client, automatically map ports, and deploy multi‑node Swarm clusters without installing anything locally, providing a fast, hands‑on way to learn Docker fundamentals.
This article explores WebAssembly’s origins, technical architecture, current browser support, limitations such as lack of OOP, garbage collection, and multithreading, and discusses its security concerns and roadmap, ultimately questioning whether it will ever supplant JavaScript in the web ecosystem.
This article explains hiproxy's core proxy mechanisms, including HTTP and HTTPS request handling, automatic certificate generation, plugin architecture, and browser proxy configuration, providing developers with a comprehensive overview of its implementation and extensibility.
This article shares a developer's transition from Android to front‑end, outlines browser engine fundamentals, essential web technologies, a simple code example, recommended tools, engineering workflow, and future learning paths to help beginners build a solid front‑end foundation.
This illustrated guide walks users through clearing cache and launching developer tools in browsers ranging from Internet Explorer, Chrome, Opera, Safari, Firefox, and Edge to lesser‑known browsers, and even shows how to toggle compatibility modes in dual‑engine browsers, with screenshots for each step.
This guide explores JavaScript's console object, detailing its logging methods, formatting placeholders, table displays, grouping, timing, and additional utilities, while providing code snippets and visual examples to help developers debug and present information effectively in browsers.
This article walks through every step a browser takes to fetch and display a website—including DNS cache lookup, OS and ISP resolution, TCP handshake, HTTP request handling, and the rendering pipeline—while also clarifying core concepts such as callbacks, async vs sync, and the event loop.
This article explains the internal architecture of modern browsers, covering their core components, network request flow, the critical rendering path, DOM and render tree construction, layout and repaint processes, and practical performance optimization techniques for front‑end developers.
From typing a URL to seeing a page, browsers perform a complex series of steps—including network requests, HTML and CSS parsing, DOM and render tree construction, layout, painting, and script execution—while handling errors and optimizations across components such as the UI, engine, networking, JavaScript interpreter, and storage.
This article explains what FPS and 60 fps mean, walks through the browser's rendering pipeline from HTML/CSS to the render tree and layers, and provides practical techniques such as avoiding forced synchronous layout, using transform/opacity, GPU acceleration, requestAnimationFrame, and proper event handling to achieve fluid animations.
This article compiles essential frontend interview questions, key knowledge areas, and detailed explanations covering HTML, CSS, JavaScript, browser engines, storage APIs, and best practices, helping beginners build a solid foundation and prepare effectively for technical interviews.
This guide introduces WebAssembly and its ecosystem—explaining how Emscripten compiles C/C++ to asm.js or .wasm, how Binaryen converts asm.js to the final binary, and provides step‑by‑step Ubuntu installation, simple hello‑world compilation, build‑process wrappers, and real‑world examples such as FFmpeg, SQLite, and game engines.
Discover how using the dedicated development browser Blisk, combined with BrowserSync’s automatic reload feature, can streamline debugging, isolate tabs, manage cache, and preview responsive designs across multiple devices simultaneously, enhancing efficiency for front‑end developers.
This guide explains what Axios is, why it outperforms jQuery for HTTP requests, and demonstrates core operations such as GET, POST, custom headers, interceptors, parallel requests, and installation for both Node.js and browsers, providing ready‑to‑use code examples.
This article explains how entering a specially crafted data:text/html URI in the browser address bar creates a temporary, editable HTML page, and shows multiple community extensions that add syntax highlighting, theming, and custom behaviors using Ace editor and other tricks.
This article explains why web pages become sluggish, breaks down the browser's rendering pipeline, details how reflow and repaint affect performance, and provides nine practical techniques—including batching DOM operations, using requestAnimationFrame and requestIdleCallback—to dramatically improve page speed and achieve smooth 60 FPS animations.
From typing a URL to rendering a page, this article walks through each step—browser DNS lookup, HTTP request and response, redirects, server processing, content delivery, and asynchronous calls—revealing the complex interactions that make modern web browsing possible.
This article explains the Navigation Timing API's full set of timestamps—from navigationStart to loadEventEnd—detailing each metric's meaning and when it records a value, helping developers diagnose page‑load performance and how they differ for same‑origin versus cross‑origin requests, redirects, and cached resources.
This article explains the steps from a client’s HTTP request to server response, analyzes performance bottlenecks such as TCP connection overhead, and presents practical browser‑side caching techniques—including Keep‑Alive, Last‑Modified/If‑Modified‑Since, ETag/If‑None‑Match, Expires, and Cache‑Control—to improve web site speed.
This article explains how the browser’s UI thread manages a task queue to sequentially process UI‑update operations, illustrated with a button‑click example that creates multiple tasks and demonstrates the thread’s idle‑time processing of queued updates.
This article walks through every step that occurs when you type a URL— from the browser’s DNS lookup and HTTP request, through server processing, redirects, HTML rendering, and subsequent resource and AJAX calls—revealing how browsers, servers, and CDNs cooperate to deliver a web page.
This article explains the internal architecture of modern browsers, describing their main components, high‑level structure, communication mechanisms, rendering engine workflow, HTML/CSS/JavaScript parsing, error‑tolerance strategies, and style computation, using examples from Firefox, Chrome, and Safari.
This article explains the browser rendering pipeline, the differences between repaint and reflow, and provides practical tips and code examples to minimize costly layout recalculations for smoother web page performance.
