March 2025 Baseline monthly digest  |  Blog  |  web.dev

[ad_1]

Jeremy Wagner

Published: March 31, 2025

Another month has gone by and since the last Baseline monthly digest, a lot has happened! In this edition, we’ll recap some posts we’ve published here on web.dev, some Baseline Newly available features that have landed, and some updates to tooling in the community.

Table of Contents

ESLint 0.6.0 has been released

Recently, we posted about ESLint launching support for linting CSS. Part of this launch included a new ESLint rule—require-baseline—for linting the CSS features you use in your project, and whether they reach a specific Baseline threshold.

Recently, ESLint launched version 0.6.0 of the @eslint/css package, which includes an important new update that renames the require-baseline rule to use-baseline. While this update is seemingly a small one, it improves on the readability of the rule. There are also some other important features and bug fixes in this release, such as the added capability of the use-baseline rule to lint nested CSS blocks. If you’re using a prior version of @eslint/css, check out this update!

How to query the Web Platform Dashboard

Earlier this month, we published a post about querying the Web Platform Dashboard. This dashboard can be queried on its frontend, as well as through an HTTP API. This can be potentially useful for Baseline tooling, as you can query the API to find features that have reached a specific Baseline threshold.

This API can be useful for tooling where you need to quickly get information about specific features. For example, you could use this type of tooling to write a script that tells you on some interval which features have become recently Baseline Newly available or Widely available. If this sounds like something useful to you, give the post a read!

How to think about Baseline and polyfills

Baseline’s mission is to bring clarity to which features you can safely use—but even with that added clarity, you still have to think about how to adopt features in a way that makes sense for your web applications. Polyfills are a big part of that process. Baseline doesn’t consider polyfills in whether features are Newly or Widely available, and it doesn’t try to tell you whether to use them. That decision is specific to your application, but it’s an important consideration!

Recently, we published a post on how to think about Baseline and polyfills, and we think it provides a helpful framework for how to think about using them. The hope with features that become Baseline Newly or Widely available is that polyfills become less of a necessity. There’s no doubt that polyfills are useful tools in your development toolbox, but they have disadvantages—they can have a negative impact on your website’s performance, and in some cases, there can even be accessibility concerns. Hopefully this guide helps you to navigate this tricky question!

contenteditable="plaintext-only" is now Baseline Newly available

The contenteditable attribute on an HTML element allows the user to change its contents as though it were a text field. This means, for example, you could place the attribute on a element and the user can interact with it like a