ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #chrome
Replace window.onscroll with Intersection Observer in Chrome to reduce main-thread load and trigger lazy loading before elements enter the viewport.
Use Chrome DevTools Protocol to intercept and rewrite HTTP requests programmatically, inject auth tokens, block trackers, and simulate failures without browser extensions.
Chrome gives each cross-site iframe its own renderer process to block side-channel attacks. Learn how to confirm isolation with Task Manager and measure the memory overhead on your own pages.
Learn why Chrome automatically switches to HTTP/3, how to confirm a request is using QUIC, and the caveats you need to watch for when deploying to production.
Chrome 80 made SameSite=Lax the default for cookies without an explicit attribute, blocking them in unsafe cross‑site POSTs. Learn how to detect the change, update cookies with SameSite=None; Secure, and verify the fix in DevTools.
Chrome 116+ auto-negotiates HTTP/3 when servers support QUIC. Learn how to decide whether to deploy it, validate with DevTools and command-line tools, and plan for UDP-blocking networks.
Service Workers let Chrome‑based sites stay fast and functional offline. This guide walks through the problem they solve, how to register one, a real‑world cache‑first example, and the trade‑offs you’ll need to manage.
Explore how Chrome's Site Isolation architecture prevents speculative execution attacks like Spectre by moving the security boundary from the tab to the site, and why this increases RAM usage.
Chrome DevTools Performance panel reveals JavaScript bottlenecks through flame charts, long task detection, and paint correlation. Learn to diagnose runtime issues and apply targeted optimizations.