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

  • 🎬 Build performant, screen-reader accessible canvas experiences → https://goo.gle/4dV0Km1 Up to now, drawing directly to a canvas meant introducing hacky workarounds to keep web features like text selection, find-in-page, and screen reader compatibility. The HTML-in-Canvas API eliminates that trade-off by letting you rasterize DOM elements into canvas pixels while preserving hit testing and interaction geometry. In this deep dive, Natalia walks through the essential steps to implement this feature across 2D, WebGL, and WebGPU contexts: preparing your canvas, drawing the HTML elements into it, understanding the new paint events, and updating geometry to keep focus rings aligned. Check out the video to see implementation examples and framework resources! ⬇️

  • Important updates for the Email Verification origin trial, including a new dedicated docs section → https://goo.gle/4s5Y2Qb 📱 Chrome for Android support enabled (Settings > Addresses and more > Verified Email) 🔑 Third-party origin trial support for embedded identity SDKs (same-site issuer requirement) 🛡️ JWKS signature validation guidance for optional `kid` claims 🔤 Strict exact-case email claim matching coming in Chrome 156 🏷️ Header standardized to 'Sec-Fetch-Dest: email-verification'

    • No alternative text description for this image
  • That failing API call in the Network panel? Rewrite it in the Console in two clicks → https://goo.gle/4i2xbRL Right-click any request and select "Edit and resend as fetch". DevTools opens the Console with the fetch() call ready to edit, parameter comments included, and a reference link. 🔒 Also new: local overrides block path traversal and non-http(s) schemes like data: and blob:

    • No alternative text description for this image
  • Chrome for Developers reposted this

    Open-source contributions are always welcome! 🙌 I got a few questions recently about contributing to our WebMCP projects, so I recorded a quick video with some example starting points. 💪 If you have your own ideas and want to chat about them before diving in, feel free to reach out. I’m always happy to talk! 😀 • Tools: goo.gle/webmcp-tools • Extension: goo.gle/webmcp-extension #WebMCP #AgenticWeb

  • Upgrade your coding workflows with current web best practices → goo.gle/mwg Animating modals and overlays can be tricky, often resulting in messy z-index workarounds or fragile JS timers to handle exit animations. Modern Web Guidance helps with this by providing your AI coding agent with curated guides for @starting-style blocks, discrete display transitions, and proper top layer rendering. Watch our side-by-side comparison to see how a guided agent produces a cleaner solution out of the box.

  • Chrome for Developers reposted this

    Ive been having a lot of fun going through the WebMCP hackathon winners. One idea showed up in several of them: do the math in your tool code, and give the model a simple answer. WebMCP tools run inside the web page, so they can use the GPU, draw on a canvas, or run plain JavaScript before replying to the agent. Some examples: 🧠 Faraday (MRI viewer) uses WebGPU to crunch brain scan data. The agent asks for sizes in milliliters, and the page does the conversion. The scan stays on the users machine. 🏠 Alza (floor plan editor) checks for furniture collisions and replies with short codes like door-blocked. The agent moves things around until no issues are left. 💐 Bouquet Studio measures the arrangement and returns numbers, like how visible each flower is and how much space is still empty. The tool description sets targets for both. 🖌️ MASIL (calligraphy studio) draws each brush stroke off-screen first and checks that it will actually be visible. What I like about this: the model is good at deciding what to do next, and code is good at math. Splitting the work that way plays to both. Numbers cant capture everything about how something looks, but they give the model a clear target. Great work from all four teams! 👏 Repo links are in the comments. Have you tried anything like this in your own tools? Id like to hear how it went. Also, thank you to all the Hackathon judges for surfacing all the cool app! Sarah Drasner Alex Nahas Kasper Kulikowski #WebMCP #WebDev

    • No alternative text description for this image
  • JPEG XL officially landed in Chrome 155 → https://goo.gle/4yYpSjW Here is a quick breakdown of why this next-gen image format matters for web performance and security: 1. 30–50% File Size Reduction: Dramatically shrinks image payloads compared to legacy JPEGs while preserving visual fidelity. 2. Native HDR and lossless JPEG transcoding: Upgrade existing JPEG archives losslessly without re-encoding quality degradation. 3. Pure Rust Decoder (jxl-rs): Eliminates memory safety bugs without compromising SIMD hardware performance. 4. Interop 2026 Aligned: Shipped in response to top web developer proposals across the browser standards ecosystem.

Affiliated pages

Similar pages