Prepare your website layout for the future of autonomous web interaction → https://goo.gle/4fvmHrE AI agents accessing your site rely heavily on a well-formed accessibility tree, descriptive tools, and stable layouts to navigate effectively. A single malformed tool definition or an unexpected layout shift can break an entire agentic workflow. Discover how to run the new agentic browsing audits in Lighthouse through DevTools for agents to verify your application is completely ready for autonomous traffic.
Chrome for Developers
Technology, Information and Internet
Helping you build, grow, and innovate on the web.
About us
The official Chrome for Developers LinkedIn account from Google. We want to help you build beautiful, accessible, fast, and secure websites that work cross-browser, and for all of your users.
- Website
-
https://developer.chrome.com/
External link for Chrome for Developers
- Industry
- Technology, Information and Internet
- Company size
- 5,001-10,000 employees
Updates
-
If you build document editors, spreadsheet tools, or any web app where copying and pasting is a core interaction, you know that pasting needs to feel instant. Historically, reading the clipboard meant fetching all available representations of the data (HTML, plain text, images, custom formats) all at once. If a user had a massive 50MB image on their clipboard but your app only needed the plain text, that payload was still fetched and held in memory. Enter Selective Format Read. In collaboration with the Web Editing Working Group and the Microsoft Edge team, Chrome is updating the Async Clipboard API to only enumerate formats upfront, reading the actual bytes on demand. The Benefits: - Lower Latency: Expensive tasks like HTML sanitization only happen for the formats you actually request. - Reduced Memory: Drastically limits renderer process bloat during heavy paste actions. - Automatic: Every site gets these performance wins out of the box—no code migration required. Read the full breakdown on Chrome for Developers to learn how it works and how to handle lazy-loading edge cases → https://goo.gle/4wweJFZ
-
-
Learn how Japanese IT company CyberAgent automated fixing runtime errors with Chrome DevTools MCP → https://goo.gle/4fTVM94 Addressing runtime errors manually across hundreds of UI components is tedious and error-prone. CyberAgent connected the Chrome DevTools Model Context Protocol (MCP) server to an AI agent, allowing it to interact directly with the browser, read console logs, and apply fixes autonomously. In about an hour, the agent audited 32 components and 236 stories in their Storybook-based Spindle design system, giving their team 100% audit coverage without manual intervention.
-
-
Learn how Nuvemshop fixed LCP detection to drive business growth → https://goo.gle/4fRKuDo Nuvemshop faced a unique architectural challenge: merchants could dynamically arrange homepage modules, which often confused the browser's LCP detection algorithm. To solve this, they systematically audited their core themes, removed lazy loading from top-of-viewport images, and added explicit fetchpriority=""high"" signals. These precise technical adjustments led to a 68% relative improvement in healthy LCP scores and an 8.9% increase in mobile conversion rates.
-
-
Asking users to pick between passwords and passkeys usually leads to hesitation. Amedia changed the game by pairing WebOTP with passkey creation into one seamless user gesture. → https://goo.gle/4gVEc70 Relying on manual SMS OTP verification introduces significant friction that lowers conversion rates during critical user journeys. Amedia, the largest publisher of local editorial media in Norway, addressed this issue by combining the WebOTP API with passkeys. The combination allowed their web apps to programmatically receive specially-formatted messages bound to their domain. By invoking passkey setup right after WebOTP verification, 48% of new users create passkeys and returning readers sign in 82% faster without needing manual passwords.
-
-
Read the details of the latest web features in Chrome 151 → https://goo.gle/3RtklSl Chrome 151 is rolling out now with powerful capabilities for web developers. Simplify media access with the new <usermedia> element, assign declarative shadow DOM slots manually in HTML, and capture SPA route changes using new soft-navigation performance entries.
-
-
Adapt your site for lighter notification prompts in Chrome on Android → https://goo.gle/4fVB7CN Starting in Chrome 155, we are shifting to a less intrusive notification experience on Android to address prompt fatigue. Because non-blocking prompts can time out, code that checks for granted permissions needs to monitor state changes dynamically. Learn how to update your code and implement contextual prompting for better user engagement.
-
-
🌐 Happy World Wide Web Day! Today we're celebrating how far the web has come and where it's headed next. With the latest emerging features, the agentic web is taking shape. New capabilities like WebMCP, built-in browser AI models, and HTML-in-Canvas are giving developers tools to build faster, richer, and more intelligent web experiences than ever before. What are you most excited to experiment with in your projects?
-
-
-
-
-
+5
-
-
Stay informed about the latest web platform capabilities with the June 2026 Baseline digest → https://goo.gle/4pB11im A new batch of features reached Widely available status this month, including conditional styling with the :has() parent selector, built-in canvas cleaning with reset(), and native CSS nesting adjustments using the & selector. You can also implement responsive preloading with media queries or test script availability using the scripting media feature. Read our technical breakdown to start implementing these updates in your production codebases safely. Then set up Baseline alerts so you don't have to wait for the monthly roundup.
-
-
Chrome for Developers reposted this
One of the things that we at Chrome have been thinking about is a way to do declarative route and navigation matching **in CSS**. Together with Noam Rosenthal and L. David Baron I’ve been working on it for the past few months, and next week we’ll be presenting our work at the CSSWG F2F meeting. In https://lnkd.in/e9kJWabc I jotted down a quick intro to the concepts that we’ll be introducing: 1. Define Routes with @route 2. Query the navigation with @navigation 3. Select the navigation trigger with :nav-source 4. Advanced link selection with :link-to() (And url-pattern() woven throughout) We already did an initial pitch of this at CSS Day back in June, and a quick read of the room confirmed we were on to something. More feedback can’t hurt of course, so please reach out (or leave a comment at the CSSWG issue) if you have _any_ feedback 😊