Chrome for Developers’ cover photo
Chrome for Developers

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/
Industry
Technology, Information and Internet
Company size
5,001-10,000 employees

Updates

  • 👀 Tune in tomorrow at 5PM CET / 8 AM PDT on twitch → https://goo.gle/47lXcFI

    The Agentic Web is happening live! 🔥 This week we have a special guest! 🎉 Together with André Cipriani Bandarra we are thrilled to welcome Nart Madi, CEO and Founder of Senro 🎉 We will be discussing WebMCP Evals, Observability, and way more 😉 What does "production-ready" mean for the Agentic Web? We’re diving deep into the tooling and testing patterns you need to know. 🕒 When: Friday at 5 PM CET / 8 AM PDT 🎥 Where: Live on twitch.tv/theagenticweb/ See you there! #TheAgenticWeb #WebMCP #Evals

  • Same visual result, a fraction of the JavaScript code 📈 Modern Web Guidance helps your agent generate clean web code by pulling best practices directly into its context window. Instead of creating repetitive JavaScript event listeners, your agent learns to use declarative attributes like `commandfor`, alongside reliable browser fallbacks. Give your agent Modern Web Guidance and build cleaner apps with less code → goo.gle/mwg

  • Chrome for Developers reposted this

    Your coding agent probably still opens dialogs with JavaScript. It doesn’t have to. In this latest video, I show how Modern Web Guidance helps agents reach for declarative dialogs instead, using the Invoker Commands API. A button can open and close a dialog with two HTML attributes, and the browser handles the top layer and focus restoration for you. It’s supported in the latest version of every major browser making it Baseline newly available, but Modern Web Guidance gives extra info on fallbacks if you need to support older browsers 🙂 YouTube link in the comments 👇 #WebDev #AI #Chrome

    • No alternative text description for this image
  • Chrome 153 and 154 brought powerful new WGSL language extensions and Dawn performance optimizations to WebGPU → https://goo.gle/4hGkYAU Here are the key highlights for graphics and compute developers: * Direct Swizzle Assignment: Update vector swizzles directly in WGSL shaders without temporary variables. * Buffer View Extension: Safely reinterpret buffer memory at specific byte offsets using bufferView and bufferArrayView. * Extended Buffer Mapping in Dawn: Combine MapWrite with other GPU buffer usages to bypass staging buffer overhead

    • No alternative text description for this image
  • Ever since native Split View launched in Chrome 145, users have been able to view tabs side-by-side natively. But until now, extensions building multitasking or comparative experiences had to rely on complex workarounds like resizing OS windows or embedding pages inside side panels and iframes. We are excited to announce the Split View API, arriving starting in Chrome 155! Developed in close collaboration with Mozilla and browser vendors in the WebExtensions Community Group, this API integrates directly into the browser.tabs namespace without requiring any extra manifest permissions → https://goo.gle/47fdSOW

  • Clean up your third-party embeds with responsive iframes → https://goo.gle/4jT0nvM Embedding content from other sites often leads to unwanted inner scrollbars. With the new frame-sizing CSS property, an iframe can now grow dynamically as its internal content grows. Embedded documents opt-in using a meta tag and can request a resize after a content change using window.requestResize(), so widgets and comment forms can expand naturally without complex JavaScript messaging. While this feature is not implemented across all browsers, you can use it today as a progressive enhancement.

  • Chrome for Developers reposted this

    The 202609 Chrome User Experience (CrUX) release is now live on BigQuery, and we also have an exciting addition to CrUX this month! Here's a look at origins' Core Web Vitals performance this month — for the current definition of Core Web Vitals: - 68.3% of origins (↑ 0.2%) had good LCP - 81.7% of origins (↑ 0.2%) had good CLS - 85.4% of origins (↑ 0.1%) had good INP - 55.9% of origins (↑ 0.5%) had good LCP, CLS and INP This month, we are adding new experimental variants of the Core Web Vitals (LCP, INP, and CLS) including soft navigation metrics as used by SPA sites. These metrics are available in both the BigQuery data set and CrUX APIs. We have also published a detailed blog post from Annie Sullivan with details about how these data change the Core Web Vitals metrics for sites that experience a lot of soft navigations. And when we expect to migrate them out of the experimental stage. https://lnkd.in/dMM5EBQK With soft navigations included we'd see these differences: - 72.1% of origins have good LCP (↑ 5.6% from current LCP) - 85.1% of origins had good CLS (↑ 4.2%) - 87.4% of origins had good INP (↑ 2.3%) - 59.5 % of origins had good LCP, CLS and INP (↑ 6.4%) The CrUX Vis tool has also been updated allowing you to visualize the impact of the changes on a site by site basis: https://lnkd.in/g5eshKKh Use it to check out how your site's Core Web Vitals will change. We've launched these as experimental metrics for now while we continue to evaluate them, and get feedback from you all. However, barring any major issues, we're aiming to integrate them into Core Web Vitals from May next year. We'll keep you updated on that date! This is an exciting launch involving years of work and we think that it can finally help us understand the true performance impact (+ve AND -ve) of SPAs. We look forward to the discussion on both individual sites, and with the BigQuery dataset, analysis across the web as a whole!

  • Declarative dialogs in HTML let you ditch repetitive JS event-handing boilerplate code. Which does your coding agent write? In our side-by-side test, the agent equipped with Modern Web Guidance implemented modal popovers using native invoker commands (`commandfor` and `command` attributes) because it fetched current best practices guides into its context window. The unguided agent generated four separate JavaScript event listeners, resulting in significantly more code. Give your agent up-to-date web best practices by installing Modern Web Guidance today → goo.gle/mwg

  • Chrome for Developers reposted this

    A less discussed and potentially game-changing aspect of WebMCP: helpful a11y. Assistive tech struggles with the same interfaces agents do. Dense menus, unlabeled buttons, etc. When a site has clear tools, we can expose exactly the functionality we need. I could ask it about my week, close out tasks for the day, even launch a whole product development and social campaign with my voice. Another nice part of this, is that it's progressive enhancement. You can collapse this sidebar and just use the site as you've always done if that's what you prefer. This is actively being thought through. You can see the checklist, or join discussion here: https://lnkd.in/gt2d3vMv

Affiliated pages

Similar pages