{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"A Green API Is Not a Working Page","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/faf5f0aa\"></iframe>","width":"100%","height":180,"duration":333,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/a-green-api-is-not-a-working-page.\nFive 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.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #javascript, #webdev, #debugging, #frontend, #web-analytics, #production-bugs, #ecommerce, #observability,  and more.\nThis story was written by: @ohadfarkash. Learn more about this writer by checking @ohadfarkash's about page,\n            and for more stories, please visit hackernoon.com.\nEvery endpoint returned 200. Every latency measurement was green. Meanwhile a third of the product cards had a dead click handler, a call-to-action had been inert long enough for a shopper to click it five times in 26 seconds on a session recording, and product images sat fully loaded inside cards that were one pixel tall. None of it was visible from the server, because a handler that never compiles leaves no trace there. Here is each bug, the measurement that actually found it, and the assertion I now write instead.","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}