#cssBug
Live, measured metrics for the hashtag #cssBug from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #cssbug
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mastodon.social (Mastodon public tags API) · fetched 2026-07-28 09:55 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-07-28 09:55 UTCNo related tags with measured usage found for #cssbug.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-28 09:55 UTCEverything below is measured over the latest 9 public posts (spanning ~12025 hours).
Posting hours (UTC)
Languages: English (9)
Avg boosts / post: 0.3
Top of the latest posts
Wow, WebKit moved fast on this! https://bugs.webkit.org/show_bug.cgi?id=265254 Remember, if you see a problem, at the very least say something! #css #devTools #bug #cssBug #coding #frontend #webDev #webDevelopment
As exciting (and useful) all the new #CSS units are, it looks like things working as expected with them isn't a thing for now. Safari has problems with `lh` https://bugs.webkit.org/show_bug.cgi?id=267185 and doesn't seem to support `cap` (a
New #CSS featues should make our lives easier, right? Except for when they're buggy. Just hit (and filed) a Chrome bug 🪲 https://issues.chromium.org/issues/405676714 Live test https://codepen.io/thebabydino/pen/qEBKRej #bug #cssBug #chrome
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/cssbug