Discover how the new Baseline Features audit in Lighthouse helps you evaluate browser compatibility → https://goo.gle/3TXx3cO Located in the Best Practices section, this new diagnostic audit checks the Baseline status of web platform features used on your page. Powered by the web-features package, it detects web feature usage in your source code and in third-party scripts, and labels them as Widely available, Newly available, or Limited availability with links to webstatus.dev.
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
-
Chrome for Developers reposted this
Thank you Shanghai for an amazing I/O Connect! 🙏 Loved connecting with so many fellow builders! It's incredibly inspiring to see all the AMAZING things you are working on, like agents embedded on website, agentic extensions that can use WebMCP tools, browser automation tools, code review agents and more! 💪 I have so many things to try out now and so many blog posts to write 😂 - that’s great! At the event I had the great pleasure of giving a “Welcome to the agentic era: Is your website ready?” talk with Andrew Kean Guan, and a “Practical steps to make your website agent-ready” workshop with Carlos Giraldo. During the talk, we touched on how agents “see” your website, how to implement WebMCP tools, and how to test and evaluate them! I’ll drop some useful links in the comments 🙂 The workshop had a fun twist 😁 - We took some live requests from the audience, and after testing WebMCP tools in different languages, my IDE now gives me text suggestions in Spanish (Thanks, Carlos! 😄). A massive thank you to the organizers and everyone who made this event so special. Until next time, keep building! ✨ #GoogleIOConnect #Shanghai #AgenticWeb #WebMCP
-
-
Streamline your deployment pipelines by 5 types of website issues early → https://goo.gle/4wY1X38 When you are rushing to finalize web changes, accessibility and performance can accidentally get pushed to the back burner. By using Lighthouse within DevTools for agents, you can instruct your coding agent to run automated checks and apply fixes to code files autonomously.
-
Stop paying the toggle tax of switching between your IDE and the browser → goo.gle/4i2wPuL Chrome DevTools Connect for WebStorm brings the power of Chrome DevTools directly to your AI agent. When debugging complex multi-step state issues, your agent can open Chrome, reproduce the sequence, read console logs, apply a fix, and re-verify the result, all without asking you to leave the editor. Built in partnership with the Chrome DevTools team using the Chrome DevTools CLI.
-
Take web apps to the next level by running streaming AI chats directly inside the browser → https://goo.gle/4wkxw6V This comprehensive tutorial guides you through using the Prompt API alongside the Vercel AI SDK UI and AI Elements. You will see how to leverage DirectChatTransport to run the loop locally without spinning up a dedicated backend server. The post also provides practical strategies for handling UI nuances, like closing open markdown syntax during live streaming tokens and establishing an automated cloud fallback to Gemini 2.5 Flash if the local model is unavailable. Dive into the setup and view the live code samples today.
-
-
Chrome for Developers reposted this
Coming soon to Chrome: a way to control scroll axis-locking! ↕️ When you scroll a 2D scroller on the web, the browser may ignore some minor scroll deltas in the non-main scrolling axis when the user’s intent was to scroll only one axis. This is known as scroll axis-locking or “railing”. While helpful most of the time, this railing sometimes gets in the way of users … and with `scroll-axis-lock: none`, you can soon (from Chrome 153 onwards) disable this axis-locking behavior 😊 (Handy for map or image zoom interfaces!) Post with all the details: https://lnkd.in/evimJs8n
-
Build on-device AI experiences using the Prompt API and Vercel AI SDK → https://goo.gle/4vSx6nw The new @browser-ai/core community provider allows you to run on-device language models directly inside the browser using standard Vercel AI SDK primitives. You can stream generated text, pass multimodal inputs like image and audio files, and generate structured JSON outputs validated with zod. For maximum reliability, you can configure hybrid setups that automatically fall back to a cloud model like Gemini 2.5 Flash whenever local capabilities are offline or unavailable. Read our latest guide to see code snippets and try the interactive demo.
-
-
Learn how NHS England improved sign-in times and saved over £1.2M with passkeys → https://goo.gle/4x2jyqs Building secure authentication at scale presents major challenges with forgotten credentials and rising SMS transaction costs. By implementing the WebAuthn API and Conditional UI, the NHS login platform enabled 6.7 million users to create passkeys. Median sign-in times dropped dramatically from 43 seconds to just 5 seconds. The team also incorporated the WebAuthn Signal API to synchronize credentials and seamlessly remove invalid keys from autofill suggestions. Read our deep dive to explore code snippets and UX lessons learned from this massive deployment.
-
-
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.
-
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
-