一位技术博主公开批评了Google Chrome开发团队在处理其提交的软件缺陷报告时的做法,认为这种缺乏区分度的批量关闭行为极不专业 1。该博主于2012年提交了一份关于Chrome在渲染内联X-bitmap格式图像时未能正确显示img标签alt文本的Bug报告,但在被忽视约18个月后,该报告被团队标记为“过时”并直接关闭 1。在关闭过程中,开发人员并未对问题进行实际验证,仅邀请用户重新提交新的报告 1。
面对这一处理方式,作者指出自动关闭报告并不等同于解决了问题,这种做法主要激怒了那些投入精力撰写包含详细测试用例的高质量报告的贡献者 1。据Chrome团队声称,他们目前拥有多达40,000个Bug报告,由于数量过于庞大而难以逐一处理 1。针对这一困境,作者建议开发团队应提供更便捷的机制,例如增加一个简单的“点击按钮重新激活”功能,或者在不显著增加维护成本的前提下保留旧报告,而不是直接将其丢弃 1。尽管文中注明相关事件发生于2012年8月,但文章头部显示的日期为2026年11月18日,这被认为是博客更新或重发的时间 1。
A technology blogger has criticized the Google Chrome development team for declaring a form of "bankruptcy" on bug reports by mass-closing them without proper resolution 1. The controversy centers on a specific report submitted by the author regarding an issue where alt text for inline X-bitmap format images failed to display correctly in the browser 1. Approximately 18 months after the initial submission, the report was marked as "obsolete" and closed, with no actual verification performed; instead, users were merely invited to resubmit if they still experienced the problem 1.
The author argues that this approach is unprofessional and discourages contributors who invest significant effort in providing high-quality feedback with detailed test cases 1. The Chrome team has cited the sheer volume of issues, claiming to manage around 40,000 bug reports, which makes individual handling difficult 1. However, the blogger contends that automatically closing tickets does not equate to solving problems and primarily alienates the community members most willing to help improve the software 1. To address this, the author suggests implementing a simple "click to reactivate" button or retaining old reports rather than deleting them, thereby preserving valuable information without significantly increasing maintenance costs 1. Although the piece references events from August 2012, it was published under a date of November 18, 2026, likely reflecting a blog update or repost 1.
评论
还没有评论,欢迎留下第一条。