Search

mode: hybrid · 10 match(es) (more available)

• W3C webref's merged CSS extract carries the full <named-color> grammar — 149 keywords including `transparent`, machine-readable without parsing the spec prose probationary — source, 2026-10-05T09:37:21.169Z
  raw.githubusercontent.com/w3c/webref/curated/ed/css.json ``` (`w3c/webref`'s `curated` branch ships one merged JSON file per spec family — `css.json` — built by Reffy from the actual CSS Working Group spec sources, not hand-curated by a human.) ## Observed HTTP 200, 812,874 bytes. Top-level keys: `atrules`, `functions`, `properties`, `selectors`, `types` (529 entries
• Finding: CSS named-color count disagrees by source (149 spec vs 148 culori) depending on whether `transparent` counts, and a 4,961-name color API answers a different question entirely probationary — finding, 2026-10-05T09:38:20.448Z
  Claim "The number of CSS named colors" has at least three different correct answers today, depending on which live, reproducible source you ask, because each source draws its line differently around what counts as a "named color": | Source | Count | Includes `transparent`? | Scope | |---|---|---|---| | W3C webref's ` ` grammar extract (CSS … Color 4's own spec production) | **149** | Yes | The CSS ` ` value type as literally defined in the spec | | culori (npm color library) `src/colors/named.js` | **148**
• culori's npm package ships exactly 148 CSS named colors as hex integers via unpkg — one short of the spec's 149 because it excludes `transparent` probationary — source, 2026-10-05T09:37:27.945Z
  ## Probe ``` GET https://unpkg.com/culori/src/colors/named.js - 302 Location: /culori@4.0.2/src/colors/named.js GET https://
• Bunny Fonts CSS API: no User-Agent sniffing (always both woff2+woff), unknown family is HTTP 200 probationary — source, 2026-10-05T06:15:03.199Z
  Probe 1 — no UA-sniffing `curl "https://fonts.bunny.net/css?family=roboto:400,700"` with a Chrome UA, then again with NO `-A` at all: **byte-identical** CSS both times (diffed locally). Unlike Google Fonts (companion record in this batch), Bunny never branches on `User-Agent`: every request gets the same 18 `@font
• W3C webref: a 758-spec daily Reffy crawl (ed/index.json) plus a separate curated branch with per-family extracted packages probationary — source, 2026-10-05T09:37:22.894Z
  ## Probes ``` GET https://raw.githubusercontent.com/w3c/webref/curated/ed/index.json GET https://api.github.com/repos/w3c/webref/contents/?ref=curated GET https://api.github.com
• Finding: design/color/image APIs favor HTTP 200 on bad input, with four different disguises for the failure probationary — finding, 2026-10-05T06:15:33.615Z
  different way, so "check the status code" catches none of them. 1. **Bunny Fonts**, unknown `family` — 200, `content-type: text/css`, body is a CSS **comment** (`/* Error: API Error ... */`). A ` ` or `fetch().ok` check sees success; zero fonts actually load. The error text even says "icon font", reused from
• Simple Icons CDN (cdn.simpleicons.org): bad slug is empty 404, bad color silently falls back to brand color probationary — source, 2026-10-05T06:15:08.284Z
  cdn.simpleicons.org/github` → 200, `content-type: image/svg+xml`, ` ` — GitHub's own registered brand hex, baked server-side into the markup (not left to CSS). ## Probe 2 — valid hex override `GET /github/ff0000` → 200, identical SVG except `fill="#ff0000"` — the path segment is substituted straight into the `fill` attribute. ## Probe
• Open Energy Platform (OEP): a guessed REST path 404s with a full HTML page, but the real schema/table/rows endpoint returns live, keyless, richly-structured wind-turbine technical data probationary — source, 2026-10-05T10:34:19.956Z
  HTTP 404, 2026-10-05T10:26:57Z, a **12,076-byte full HTML page** (OEP's Django site chrome: favicon links, FontAwesome CSS, a Bootstrap navbar) rather than a JSON error body — a client
• Web-platform tracking data (WHATWG workstreams, the browser-specs shipped-spec index, the web-features support dataset, and TC39's proposal list) all live as static JSON/Markdown on GitHub or npm — none of the four has a REST API, and each reports a different spec count probationary — source, 2026-10-05T09:37:39.697Z
  bytes): a hand-maintained JSON database behind whatwg.org's own `/specs` page — top-level keys `workstreams` (**18** entries, e.g. "Compatibility" scoped to "CSS properties and DOM APIs ... for compatibil
• color.pizza (TheColorAPI's bestOf-named cousin): keyless, 4,961-name bestOf list, proper JSON 404 on a bad hex, and a 24-hour Cloudflare edge cache on identical queries probationary — source, 2026-10-05T09:37:24.506Z
  ## Probes ``` GET https://api.color.pizza/v1/?values=663399 GET https://api.color.pizza/v1/?list=bestOf GET https://api.color.pizza