A lot has happened since Chrome shipped Same-Document View Transitions in 2023. In 2024 we shipped Cross-Document VTs, added refinements such as `view-transition-class` and VT Types, and also welcomed Safari in adding VT support. And this year … well, I wrote a post summing it all up.

If we started Chrome Dev Summit again, would you be interested in it? (huh - apparently can't do polls here...), Please reply, Yes or No, or any other answer in between.

✅ Baseline now has full feature coverage, making it easier to know which web platform features are ready to use. Build the next wave of Baseline-powered tools and compete for $10,000 in prizes → goo.gle/424SBWc

Announcing our public preview of Chrome DevTools MCP! Experience the full power of DevTools in your AI coding agent→ goo.gle/4pDE6Tk With Chrome DevTools MCP, your AI agent can run performance traces, inspect the DOM, & perform real-time debugging of your web pages.

Before, you needed a plugin to use Baseline semantics in your Browserslist queries. Now you don't! Just give it a target like `baseline widely available` and it'll work out of the box Available in [email protected] and later web.dev/blog/browser...

Show us your best tooling ideas to help developers adopt more modern web features! Join the hackathon for your shot at $10,000 in cash prizes 🔥🔥 web.dev/blog/baselin...

Scoped View Transitions are ready for testing in Chrome! SVTs expose el.startViewTransition() on HTML elements. The element creates a scope for the transition, ∴ the transition pseudo-elements are affected by ancestor clips and transforms. Multiple SVTs on separate elements can run *concurrently*.

🎉 Happy 30-month anniversary to Container Queries – in every browser since Feb, 2023. It was supposed to be impossible, but here we are! Why 2.5 years? Nothing will change tomorrow, but Baseline uses this milestone to signal confidence a feature has gained "wide" support. youtu.be/bhHV0rQ3-CQ

I know some people in the web community are concerned that Baseline will discourage devs from using new features—or anything not "Widely Available". Personally, I'm not worried about that at all. If anything, I think Baseline will speed up new feature adoption! Here's why 🧵

What new web features are your users actually ready for? Stop guessing. 🔮 Baseline helps you make data-driven decisions so you can ship the right features at the right time. Learn more and find your target with #WhatsMyBaseline → goo.gle/whats-my-baseline

Firefox shipping scheduler.postTask() and scheduler.yield() for all your long task-avoiding scheduling needs!!

Here's my talk from I/O along with the companion blog post that rounds up all of the links mentioned. It's been a very exciting year for the web, and all the new Baseline tooling we've just announced can help you understand when to adopt these new features. web.dev/blog/whats-n...

We've just published v5.0.0 of the web-vitals JavaScript library for measuring Core Web Vitals. github.com/GoogleChrome... As a major release, this includes a number of breaking changes as detailed in the upgrading doc: github.com/GoogleChrome... Please read carefully before upgrading. 1/5 🧵

So sad... One of the happiest things about building new CSS features was having Adam build cool stuff with them.

After 6 years of working closely alongside @nerdy.dev I am just rocked by this news. Still not ready to accept it TBH but I stand behind Adam as one of the most genuine, talented, effervescent devs I've ever worked with. If you're hiring snatch him up before I figure out a way to get him back 👀

Adam is the brightest, most authentic, inspiring, truly creative, high performing, deeply passionate, and nice person I have ever worked with. And then my employer decided to terminate his role. I am gutted and sick to my stomach. I will miss you, my friend 💔

It’s a sin that this happened to Adam. A true world class frontend engineer and a world class human. I remember being so excited when we first spoke about him joining Chrome and then talking VisBug. And he’s gone from strength to strength. What an epic own goal.

Someone hire this guy. He's one of the best. Hire him before someone else does.

G̶o̶o̶g̶l̶e̶r̶… ex-Googler. nerdy.dev/ex-googler

Browser support info for CSS properties in VS Code is about to get a huge improvement Instead of looking at a list of browser versions and guessing if you can use a feature, now it'll just... tell you! Coming soon to the April 2025 stable release, or you can try it now in Insiders

My team is hiring! Come join us as a Developer Advocate at the intersection of Web, Chrome, ChromeOS and Android. The position is in Waterloo - Canada www.google.com/about/career...

We don't have an official CrUX Bluesky account, so for the moment I'll announce the monthly releases. And we're starting with a big one! 🆕 The 202501 release is now live on BigQuery! Check out the announcement post for the full info: groups.google.com/a/chromium.o... Highlights below 👇 🧵 1/10

We're shipping the new `Node#moveBefore()` API in Chrome 133! Read more in our latest blog post: developer.chrome.com/blog/movebef... Huge thx to @nomster.bsky.social for help bringing this to life, frameworks that helped test it, and the spec ecosystem for working with us to get it standardized!

For 12 Days of Web I answered a question that I've answered from stage in presentations but not written about: "Why not include polyfills in Baseline?" I also describe how Baseline can help you to decide what and when to polyfill 12daysofweb.dev/2024/how-to-...

Would you want core web vitals In Safari? Can you help me understand how you would use them and why numbers in one browser isn’t enough? (These may sound like silly questions, but I’d love to understand *your* specific context and use cases)

A post about how I try to meet the needs of a browser DevRel team that need to share information about new things, with those of developers who need to know what works now.

My analysis of the State of CSS and State of HTML 2024 surveys: https://patrickbrosset.com/articles/2024-11-08-state-of-css-and-state-of-html-2024/ Some very interesting take aways in there!

More people are using container queries than I realized! This is a great thread listing some of the sites using them in production, and also some graphs that show some clear positive trends 😄

Great post by @joshwcomeau.com on why CSS containment is needed for Container Queries: bsky.app/profile/josh... But I need to somewhat disagree with the premise that "none of us are using them" :) If you look at the data, many popular sites already ship CQs in production! Here's a quick look: 🧵

It's amazing to see how LCP and INP have improved over the past two years by country.

@sachagreif.bsky.social not sure if you're the best person to ping about this, but today I noticed the percentages in the State of HTML survey look off (e.g. the numbers are all very small and don't add up to 100). 2023.stateofhtml.com/en-US/featur... Do you think this may be a bug?

We've updated our 9 recommendations for the most effective ways to improve CWV web.dev/articles/top... (new URL too!)

I'm building a web perf starter pack but I'm still looking for folks to add - please let me know who I'm missing because I haven't found them all on bsky yet go.bsky.app/RVWSVqe

📢 New post: The State of ES5 on the Web. For years, we defaulted to transpiling to ES5 in order to support IE. But is that still necessary? I took a look at the data to find out, and I'll just say that the results were *actually* quite surprising! 🙀 philipwalton.com/articles/the...