4 ms·
Looking at the comments on this bug, I'm pretty impressed with the Chrome teams response. Sure, it's bad that this made it into a release in the first place, b
by londons_explore 7y ago
Looking at the comments on this bug, I'm pretty impressed with the Chrome teams response.
Sure, it's bad that this made it into a release in the first place, but when it did, they were quick to identify the issue, halt the release, find 2 potential fixes, manually test the fix, get a canary release out to get wider testing, update the test bench to prevent this class of bug happening again, and start rollout to the public stable build.
All that across tens of team members, with regular status updates from humans and bots, and despite the fact no bug reporter could give them a proper repo testcase for a long time.