TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Prevent data: URLs from being used for XSS

28 点作者 lucasgonze大约 7 年前

6 条评论

lucasgonze大约 7 年前
This bug is almost old enough to drive.<p>I submitted an earlier version of it back in the early 00s and have been CC&#x27;d on the endless procedural back-and-forth ever since. Incredibly, nobody ever said &quot;we&#x27;re just not doing it.&quot;<p>One for the book of world records, Oldest Bug category.
ataylor32大约 7 年前
This reminds me of &quot;MySQL Bug #20786 gets cake&quot;:<p><a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=oAiVsbXVP6k" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=oAiVsbXVP6k</a>
评论 #16962382 未加载
favorited大约 7 年前
Ahh the rare self-closing bug. Keep the ticket open long enough, and maybe the standards group will adopt your behavior!<p>It&#x27;s cool that the large browsers had standardized on the same non-standard behavior. Makes total sense for WHATWG to adopt it, right?
评论 #16962585 未加载
评论 #16962556 未加载
ryandrake大约 7 年前
Most places I&#x27;ve worked, the older a bug is, the less likely it will ever be fixed. The reasoning goes &quot;users have lived with it for this long, so it must not be important.&quot; And we have regressions in the code that&#x27;s about to go out that have not faced users yet--fix them first.<p>Has anyone ever successfully argued for going back and fixing ancient bugs, prioritizing it over fixing more recently-discovered bugs? What argument did you use?
评论 #16962701 未加载
评论 #16962478 未加载
jld大约 7 年前
Nothing like fixing a bug by changing the spec.
esbafb8大约 7 年前
14 years ago, it was reported on... Windows XP. PS: I do miss XP.
评论 #16962620 未加载