What was your favorite part of #GoogleIO this year? 🎤 We hit the event floor to ask developers what announcements, sessions, and moments stood out to them the most.
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 149 is officially live, delivering cleaner layout styling capabilities and an enhancement to navigating pages that use WebSocket connections to improve the user experience → https://goo.gle/4uSvj2a We’ve shipped stable support for CSS gap decorations, allowing you to style gaps in container layouts like grid and flexbox natively. You no longer need to rely on hacky borders or pseudo-elements; this feature is progressive-enhancement friendly and lets you easily animate rule widths, colors, and insets. On the performance front, active WebSocket connections will no longer prevent your pages from entering the Back/Forward Cache (bfcache). Chrome now proactively disconnects active WebSockets on cache entry so pages can be stored in memory and instantly restored when navigated back.
-
We are introducing some of the biggest changes to HTML in decades. With Declarative Partial Updates, you can now render out-of-order HTML updates and build complex UI placeholders entirely without JavaScript → https://goo.gle/49Bz9nK If you have application logic that isn't visible until a user interacts, you can load it at the end of the document and patch it after the page renders the critical content. Plus, the new streaming APIs for dynamic markup makes Island architecture easier than ever. By using streamHTML and streamHTMLUnsafe, you can fetch and stream HTML directly into the DOM. Both APIs are available for testing in Chrome 148.
-
Chrome for Developers reposted this
TL;DR Join the HTML-in-Canvas developer newsletter mailing list so you don't miss important updates to the API: https://lnkd.in/e-rWSYMY ✉️ We saw such contagious enthusiasm for the HTML-in-Canvas API at our Google I/O demo booth! Your feedback, along with the number of sites that joined the origin trial, is a great signal of the community's interest. As you might know, origin trials are run for new or experimental features. They are a great way to collect developer feedback to ensure the feature meets developer expectations. It also means that the feature is in an early stage of development, and implementation details may change based on the feedback. This article explains the concept in detail: https://lnkd.in/euyQfXij Since HTML-in-Canvas is currently in an origin trial, I recommend subscribing to the developer newsletter so you don't miss any important technical updates and can ensure your implementation works across different browser versions.
-
We released an experimental, spec-compliant polyfill for the Prompt API, so you can start building your web AI features today. When the API isn't natively supported, it defaults to using Transformers.js with Gemma 3 1B for local execution, but you can easily configure it for cloud backends or other local models. It requires minimal changes to your workflow, just conditionally import the polyfill, create your session, and call your prompt.
-
Chrome for Developers reposted this
In case you missed the Google I/O session by Nina Satragno and me on modern best practices for user authentication on the Web, you can watch it here: https://lnkd.in/euzNU74Q
Modernize authentication with passkeys, digital credentials, and more
https://www.youtube.com/
-
Testing systems that use generative AI requires a new approach. Because models produce probabilistic outcomes, a single user input can lead to thousands of different answers with varying degrees of accuracy. We just released a guide on WebMCP evals to test your system's exact touchpoints with an LLM. This allows you to systematically verify that a model understands your tool's purpose based on its schema and correctly acts upon the information it receives. Check out the full guide to see how to verify that agents pick the right parameters for user intent and successfully fulfill entire user journeys → https://goo.gle/4ftQUZI #GoogleIO
-
-
Chrome DevTools for agents changes how AI optimizes your web apps. Instead of letting a coding agent guess from static source code and burning tokens, this allows your AI to run actual performance traces and agentic web Lighthouse audits in a real browser. #GoogleIO
-
AI coding tools are incredibly powerful at writing code, but they are often disconnected from its execution. They can generate a complex web app, but they cannot observe its behavior or inspect its output in a live browser. Chrome DevTools for agents provides your coding agent with the visibility it needs to verify, debug, and optimize code in real time. A couple of months ago we showed it for the first time, and now we are excited to announce that Chrome DevTools for agents is now available as a stable 1.0 release → https://goo.gle/42K7Rrl #GoogleIO
-
-
Lighthouse is getting a new agentic browsing category. Instead of just auditing for human users, it tracks WebMCP schemas and layout shifts to see if AI agents can actually navigate your site. If machine-readability is on your roadmap, this is worth a look → https://goo.gle/3ReK3JD #GoogleIO
-
