The browser-compat-data project (used by MDN, caniuse, and tools) now has:

20,000 commits
1,123 contributors
465 releases
19,148 data entries

That's what comprehensive web compat data looks like.

And it takes well funded teams at @openwebdocs.org and @mozilla.org plus amazing contributors.

A bit of a vulnerable post by me but we need your help to get us through what has been a more difficult period than 2020.

It would be really appreciated if you could read and share in your networks too 💛

bell.bz/its-been-a-v...

I’ve been working on Accessibility Compat Data since around May 2025. Here’s what’s happened since then & what’s going to happen in 2026! Spoiler: there’s lots to be excited about 🥳

lolaslab.co/blog/2025/ac...

I don't know enough of the technical details of this API to know. But I 100% agree with "I’m surprised why there hasn’t been any concrete suggestions to improve things". Little/no involvement from other implementers. This API (and others like it) is needed, yet no one else is trying to improve it.

Too many times has the privacy excuse been used to block shipping a web feature, when the native counterpart of that feature has fewer guardrails and far less transparency.

This comment from Espruino on Web Bluetooth is 😘

Web Bluetooth has been avail. on billions of devices, for several years, and I can't seem to find any instances of abuse. In the mean time I've lost count of the times hardware I've purchased has required me to install a dubious app to make it work.

It took a while, but the State of JS 2025 survey results are now live! 2025.stateofjs.com/en-US

Thanks to @danielroe.dev for contributing the conclusion.

All good questions. I didn't get a chance to explore this further. But the idea of a tax seems appealing. Projects spend so much time chasing funding opportunities, and in the end it rarely leads to something steady. A tax feels like a better approach.
opensourcepledge.com feels on the right track.

Should the entire web ecosystem, all of us, pay a tax to maintain the open source docs, data, and tools we all rely on to build for the web? After all, this is the infrastructure that makes it all possible, and it needs maintenance.

Inspired by a great talk by Marga Manterola at #fosdem

Yeah. Sorry. This can be quiet cryptic. The main thing to check, if you’re interested, is the name and description fields in the new filter-function.yml file. They’re supposed to make sense to developers. Do they make sense to you?

If the feature you’re looking at on Can I Use doesn’t have the little developer signal 👍 icon, let me know. We’re probably missing it in the backing data.

We are already adding it in this PR : github.com/web-platform...

If you attended my talk at #fosdem today, on web-features and browser-compat-data, and on how these critical data sources shape our experiences as web developers, without us even realizing it, then here are the slides:

patrickbrosset.com/talks/

Great read. And really cool project. The comparison to view source surprised me knowing you didn’t have to actually view any of the source, but I agree with the renewed creativity spark.

Help prioritize the web features you need most → goo.gle/4iVDhCk

The WebDX Community Group is launching a direct way for you to upvote features on sites like Can I Use and web.dev to signal demand to browser vendors.

🎉 Live from the CSS WG F2F: We just agreed to support multiple borders and outlines per element, comma-separated!

But we can’t decide on the order: inside out or outside in?
What feels more natural to you, A or B?

(it needs to be the same across borders and outlines or different box-sizing values)

Are you tired of Tech Bros snooping, and forcing A.I. on you? Do you hate them spying while you're buying? Are you bored of slop while you shop, and scurf when you surf? Then new Vivaldi 7.8 is for you: no A.I., built-in tracker & ad blocking, powerful, made in Europe from punk rock and Nordic snow.