Tracking CSS at the Speed of the Platform

Finding out what’s genuinely new in CSS is harder than it sounds. A quick search for “new CSS features” surfaces a lot of recycled content that still presents CSS Grid as a nascent technology, even though it has been baseline for nearly a decade. To get an accurate picture, you have to go closer to the source: browser blogs, engineering teams, and data-rich dashboards that track feature status and adoption.

The resources below cover CSS specifically, but nearly all of them also track broader web platform changes in JavaScript and HTML.

Start with the Browser Vendors

The companies actually shipping browsers publish detailed engineering blogs, and several are excellent for CSS-specific updates. Google’s web.dev blog is a solid starting point, especially Rachel Andrew’s monthly “New to the web platform” recaps:

WebKit maintains a dedicated CSS category on its blog. The publishing cadence is less frequent than web.dev, but the write-ups are deep. A good example is Jen Simmons’ breakdown of text-wrap: pretty.

For Firefox, the Firefox Nightly News blog covers what’s landing in the browser, while the Microsoft Edge blog does the same for Edge.

Community Hubs and Aggregators

Independent publications remain central to the CSS discourse. Notable outlets include Smashing Magazine, the Frontend Masters Blog, Piccalilli, and CSS-Tip. CSS-Tricks itself also maintains an almanac of CSS features.

Following all of these individually can get unwieldy. Frontend Dogma aggregates curated links from these sources and many others into a single, updated list.

Structured Feature Dashboards

If you prefer structured data over blog posts, dedicated dashboards are more effective.

Web Platform Features Explorer

The Web Platform Features Explorer organizes features by their Baseline status, helping you see what is newly available across the major browsers at a glance.

Web Platform Status

For richer filtering, the Web Platform Status dashboard lets you narrow down by Baseline year, or even isolate features that were highlighted as top CSS interop pain points in the latest State of CSS survey.

The dashboard also shows adoption rates as a percentage of Chrome page views that use a given feature. For example, you can see the uptake of the popover attribute. One caveat: adoption statistics can be skewed by a small set of very large sites—Facebook and Google alone represent a huge share of measured page views, so a single platform adopting a feature can significantly spike its metric.

The stats section of Web Platform Status also has what Lea Verou calls the “chart of shame,” which calls out browsers that are slower than their peers in adopting new features.

Chrome Platform Status

The Chrome Platform Status dashboard surfaces the same adoption data with even more granularity, including usage among top sites and sample URLs of sites currently using a given feature.

Going Deep on Experimental Features

For what is actively being developed, the Polypane browser provides a host of developer tools. Polypane also maintains an experimental Chromium features explorer that breaks down upcoming features by the Chromium version they will land in.

For commentary and practical walkthroughs, Kevin Powell’s YouTube channel is a staple. In addition to video recaps of new features, he publishes weekly HTML and CSS tips on a dedicated site.

Primary Sources and Release Notes

For the absolute ground truth, observe the standards process and browser release cycles directly.

CSS Working Group

The CSS Working Group publishes every working draft as it evolves. You can subscribe to its public mailing list for discussions, or syndicate updates via its RSS feed.

Release Notes

Each major browser ships release notes with each new version, giving a predictable pulse for when features go live:

Supplementary Tools

A few more utilities round out the toolkit, each from a different angle:

  • BCD Watch: Igalia’s BCD Watch tracks changes to MDN’s browser-compat-data repository, which is the canonical record of what feature ships in what browser.
  • HTTP Archive Web Almanac: Recent editions are tighter on dedicated CSS coverage, but the 2022 edition had a CSS chapter, making it useful historical context.
  • caniuse: The news section is not frequently updated at present, though it could be a future source of change logs.
  • IntentToShip bot: Available on Bluesky, Mastodon, and Twitter, this bot posts whenever a browser vendor ships or alters a feature—useful for real-time alerts.

Ask an AI, Then Verify

ChatGPT can also serve as a starting point. A straightforward prompt like “What are the latest CSS features that have either become supported by browsers in the past year, or will soon become supported?” yields reasonable leads. The key is treating the answer as a hypothesis to check against the dashboards and blogs above, not as the final word.

Combining these sources—vendor blogs for narrative, dashboards for structure, and compat data for truth—covers the territory well enough that not many features will slip through unnoticed.