Published: February 27, 2025
It was a busy month for Baseline in both the community, at Google, and other major browser vendors. In this edition of the Baseline monthly digest, we at Chrome Developer Relations once again take a moment to review recent developments, such as updates, community articles and talks, tooling, and anything Baseline-related we think you should know about!
Interop 2025 is underway
Every year, the Interop project defines a set of focus areas that major browser vendors and supporting organizations collaborate on to land new features across all browsers within the same year. In February, the Interop 2025 project was officially launched as a joint effort:
- Apple's blog post
- Mozilla's blog post
- Microsoft's blog post
- Google's blog post
- Igalia's blog post
- Bocoup's blog post
Areas the project will be focusing on this year include features for Core Web Vitals, the View Transitions API, WebAssembly, Layout, and many more. Give any (or all) of these blog posts a read!
TheJam.dev fireside chat with Rachel Andrew
Recently, Rachel Andrew of Chrome Developer Relations sat down with Brian Rinaldi at TheJam.dev to talk about Interop and Baseline.
The discussion was wide-ranging, and included questions from the audience. It's worth watching, because it sets the stage for why Baseline is a thing, and how it helps web developers understand how much of the web platform is available to use without worrying about browser compatibility.
baseline-status WordPress plugin
This month, Geoff Graham of CSS-Tricks published Baseline Status in a WordPress Block, an article about the baseline-status WordPress plugin that implements the Baseline Status web component. This plugin gives you an easier way to drop the web component into pages of your site where you want to indicate the Baseline status of a given feature.
The Baseline Status web component—and the plugin that implements it—is very useful in contexts such as articles about web features, where it can be made clear whether or not a particular web feature can be used across all major browser engines. More importantly, when rendered, the web component gives you the latest possible information for a given web feature. CSS-Tricks is certainly taking advantage of the web component by implementing it across their site—for example, you can see that the documentation page for the @scope rule on CSS-Tricks implements the baseline-status plugin.
RUMVision Baseline case study
In the January edition of this digest, we announced that RUMVision integrated Baseline into their RUM solution. This is an exciting development, as it's some of the first tooling to help site owners know what Baseline features their users are able to benefit from.
This month, RUMVision wrote a case study on how they integrated Baseline into their product. It's a compelling case study, and it's worth a read if you want to know just how they did it!
The Popover API is now Baseline Newly available (again)
In April 2024, it was announced that the Popover API became Baseline Newly available. However, there was a serious bug in the implementation of this API in one browser engine that was missed, and caused the Popover API to become Baseline Newly available before it should have been.
As a result—and for some reasons you might be interested in that we wrote about—The Popover API's Baseline Newly available date was updated to be January 27 of this year.
Works in all browsers—Interoperability beyond availability
Recently, Chrome DevRel's own Mariko Kosaka traveled to Phoenix, Arizona to speak at HalfStalk Conference about Baseline. Her talk spent time defining the concept of Interoperability, how to determine when features are interoperable (across all device types), how difficult that can be without a little help, and how Baseline makes it easier for developers.
While there's currently no video recorded for this talk, you can check out Mariko's slide deck to find out more. Keep an eye out for more of us from Chrome Developer Relations speaking about Baseline at a conference near you!
ESLint now officially supports linting CSS
If you've ever used ESLint, you know that it's historically been a tool for linting only JavaScript. This month, ESLint announced that CSS linting is now officially supported by their tooling. Part of this announcement involves the require-baseline rule, which helps you enforce the use of Baseline features in your project's CSS. We look forward to more tools bringing Baseline support to web developers, so that the question of feature support is easier to understand.
That's another month in the books!
2025 so far has been a big year for Baseline and we here at Chrome Developer Relations expect many more developments in this area. Keep a lookout for the next edition of this digest at the end of next month, and as usual, you can let us know if we missed anything you think should be included here, or in a future edition of the digest.