hn.today

Google Chrome dev team declares bug report bankruptcy

blog.plover.com101 points50 comments
Screenshot of Google Chrome dev team declares bug report bankruptcy

A Chrome user reported a small but reproducible bug: when the browser displayed an image in the obscure X-bitmap format, it showed a broken-image icon and failed to display the image’s alt text. The report included a link that made it easy to check the behavior. After about 18 months without action, Chrome marked the report obsolete and closed it, inviting the user to submit it again if it was still valid. The writer argues this treated a carefully prepared contribution as disposable and shifted the work of restoring it back to the person who had already done that work.

Chrome’s team reportedly had 40,000 bug reports, many of them poor or no longer relevant. The writer accepts that managing such a backlog is difficult, but says automatic closure does not resolve the problem; it simply discards reports, including useful ones. This policy also risks discouraging the most conscientious reporters, making future submissions worse. A simple improvement would be to let reporters reactivate a closed report with a button rather than requiring them to start over. The more substantial solution, the writer argues, is to keep reports available: even if some are obsolete, retaining them costs little. The central point is that soliciting volunteer effort and then casually throwing it away undermines goodwill and makes people less likely to help again.

Read on blog.plover.com50 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Web

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.