2 posts tagged with "chrome"

The Chrome team shipped Modern Web Guidance 1.0 on November 10, 2026, and a day later published the top 10 things AI gets wrong in web development. We first mentioned the project in our Google I/O recap when it was an early preview. With the stable release, it is worth a closer look.

This post covers what Modern Web Guidance (MWG) is, how it works, what it fixes, and how it fits our recommended tech stack. Short version: the guidance is good and mostly matches what we want. But two parts need care: our component libraries already handle some of the things MWG wants to rewrite, and the default install command breaks our supply-chain rules.

Google I/O 2026 just wrapped, and Chrome's web platform announcements deserve a dedicated look. While the keynote predictably led with Gemini and Android, the Chrome team quietly shipped — or signaled — some of the most consequential changes to browser capabilities we've seen in years. If you build for the web, this was a big one.

Three themes dominated: AI built directly into the browser platform, new rendering capabilities that eliminate entire categories of workarounds, and developer tooling that acknowledges the reality of AI agents writing and testing code. None of these are incremental CSS features or minor API additions. They represent Chrome's bet on what web development looks like in 2027 and beyond.

What follows is a breakdown of the five announcements that matter most, with practical guidance on what to try now versus what to watch.