{
  "id": 8221416,
  "title": "A Green API Is Not a Working Page",
  "url": "https://urgent.news/2026/09/18/a-green-api-is-not-a-working-page",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-18T03:35:08.000Z",
  "source": {
    "name": "HackerNoon",
    "slug": "hackernoon",
    "url": "https://hackernoon.com/a-green-api-is-not-a-working-page?source=rss"
  },
  "original_language": "en",
  "account": "A green API does not automatically translate into a functional webpage. In fact, a recent experience demonstrates how bugs can persist despite green checks. The author connected a session-recording tool to a product search engine, expecting insights into user behavior. However, the tool revealed numerous JavaScript errors that had been present in production for weeks. Despite all tests being green, these errors slipped through the review process. The most problematic error, \"Unexpected identifier s,\" occurred 28 times. The webpage's click payload construction contained incorrect JavaScript string escaping, causing syntax errors when the browser compiled it. To prove this, the author created a control with a correctly formatted title and observed the handler's failure. This issue affected roughly a third of every result page, with 9 out of 24 products and 14 out of 42 products being impacted. The errors resulted in broken functionalities like favorites and sharing buttons, and no data being sent to analytics. The fix involves moving data handling out of JavaScript and directly capturing events. Another error, \"Cannot read properties of null (reading classList),\" stemmed from a renamed button, causing it to become null and throwing an error before the intended functionality could execute. This affected five clicks in a seven-minute session, demonstrating the impact of seemingly invisible issues. The third error highlighted the lack of CSS for product rows, resulting in full-width inline elements and uncapped images that were fully downloaded but invisible. Lazy loading, intended to improve performance, was found to be unnecessary for these thumbnails. The author emphasizes the importance of checking the rendered DOM after any change, rather than focusing solely on the server response. This includes verifying the order of nodes, existence of elements, decoding of images, existence of CSS rules, and other factors. By asserting that rendering issues often lie between the JSON and the pixels, the author stresses the need for thorough post-deployment checks to ensure a fully functional webpage.",
  "summary": "Five production bugs that passed every API check while the page was broken — including an HTML escape that killed the click handler on a third of the cards.",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}