3 ms·
1. It's next to impossible to make a mistake like that. 2. The mistake works out in Google's favour. 3. Difficult to give Google the benefit of a doubt anymore
by mszcz 6y ago
1. It's next to impossible to make a mistake like that.
2. The mistake works out in Google's favour.
3. Difficult to give Google the benefit of a doubt anymore regarding anything.
4. Does anyone believe what PR dept. of a large corporation says anymore?
- burnerfi5724 6y agoOne benefit of this being chrome.... is the changes are public. Here is the fix and the link the cl for the fix with a link to the cl that created the issue as well: https://chromium.googlesource.com/chromium/src.git/+/f800edbd1b50ecc13a0d3391f5f45ba9c84625be%5E%21/#F0 https://chromium.googlesource.com/chromium/src.git/+/f800edb... I'll let you judge for yourself, but this is not coming from PR.
- _qulr 6y agoThanks for the link!
- shadowgovt 6y ago> It's next to impossible to make a mistake like that It would appear that the root of this error is that Chrome is also an operating system. So in small, focused apps, yes, that's a hard mistake to make. In apps that some people are using as the main shell for their entire laptop, there's a lot of nooks and crannies for complexity to hide.