Hacker News Reader

What Unit test could have cought that ? Is this a Bug at all ?

Chrome doesn't do anything wrong, but somehow the fix still has to be done inside Chrome.

Interesting how it all starts looking like one giant app, were a small change in one part leads to failures in completely unpredictable places.

View on HN

No unit test suite can cover all situations, you actually have to "use it in anger" before shipping it to something like 50% of all web users.

Chrome is "breaking the internet" for its users, so Chrome is doing something wrong.

That's what Canary Releases are for. You roll it out to (say) 2% of your users and see whether it shits the bed. If it does, NBD, you roll it back or patch. If it's good you roll it out to everyone.

It's a spec bug: they wrote a draft spec, implemented it and pushed it to a stable release too soon.

Reply on news.ycombinator.com