LinkedIn is better on the app
Don’t have the app? Get it in the Microsoft Store.
Open the appThe 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.
External link for Chrome for Developers
Chrome for Developers reposted this
I’m hiring! I’m looking for an AI Product Partnerships Lead to join our Chrome and Web Ecosystem partnerships team. Help us shape the future of the browser and web in this AI and agentic era by driving strategic AI partnerships and go-to-market strategies for Chrome browser. 🚀 Apply here: https://lnkd.in/g8hvbE4q
The WebMCP origin trial is open in Chrome 149 → https://goo.gle/4x97wMK This time limited program offers early access to experimental platform features. By joining, you can integrate WebMCP for live testing, gather user feedback, and directly inform future iterations of the API.
Chrome for Developers reposted this
After 5 months of hard work, DevTools AI assistance has received a significant update, available in Chrome stable today. Here's 4 new updates and why it helps you immediately: 🔹 Trust: Agent walkthrough with interactive widgets enables a 1-click verification of AI steps. For expert users, this increases trust. For newer users, get a guided debugging experience. 🔹 Workflow: Copy to coding agent allows you to instantly hand off your DevTools chats to your local coding agent. 🔹 Context: AI now scans Lighthouse audits alongside Elements, Network, Performance, and Sources data. Holistic data access to DevTools means better diagnostic capabilities for you. 🔹 Speed: We've reduced AI response lengths by ~68%. No more walls of text. Shoutout to Matthias Rohmer for the recording and What's New blogpost! https://lnkd.in/dHBeGifV We're building a truly seamless human-agent collaboration experience. More to come soon. Would love any feedback of what you'd like to see, and how we can speed up your devtools workflows! #chromedevtools #devtools #devtoolsai
Chrome 149 DevTools is live → https://goo.gle/4v55cVT We’ve stripped away manual workarounds to streamline your debugging, styling, and agentic workflows. Here is what's new: 💡 Agent walkthrough & Copy to coding agent in AI assistance 🎨 CSS Code Completion from Gemini in the Styles tab 🤖 WebMCP debugging tools in Application panel 🚀 DevTools for agents 1.0 with custom tools
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 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.