3 ms·
> I know this particular bug seems to be an edge case that may happen with every browser, but when you are using Chrome, you should know that if an issue doesn'
by jedimastert 7y ago
> I know this particular bug seems to be an edge case that may happen with every browser, but when you are using Chrome, you should know that if an issue doesn't affect Google, it will likely be deprioritized a lot.
Not to be that guy, but if you take a look at the bug a fix has been merged into 77
- hu3 7y agoAnd this is why I take rants against Google and MS with a grain of salt. Top voted comment couldn't bother to read bug report. I often see inconvenient truths buried in downvotes meanwhile misinformation that apeases a vocal minority gets catapulted to the top.
- egeozcan 7y agoI've read the report. I knew about the merge. This issue has been postponed until developers started reacting aggressively, so breaking all drag and drop in iframes was nearly okay until a new version was published. When the issue is affecting users, it gets worse: The small number of them who could navigate their way into creating a chromium bug report will be waved away. I'm also not a comment, I'm a person. Thank you.
- Guidii 7y agoThe reported issue was addressed within 21 days. I'm not sure that this issue illustrates the case you're trying to make here.
- egeozcan 7y agoI respectfully disagree: Try to explain your users that they won't get drag and drop for 21 days. This would have been worse if there weren't passionate people aggressively following it. A Google account integration issue would always be more important than web pages being broken in many subtle ways. This wasn't the case when they didn't hold the browser monopoly.
- techntoke 7y agoTry to explain to your users why all their add-ons were disabled because you forgot to renew a certificate.
- egeozcan 7y agoMessing up and immediately reacting is totally something else than ignoring your users.
- danShumway 7y agoAnd? Did Mozilla take 21 days to fix that issue, push it off for a future release, and only reprioritize it as a hotfix after being hounded? GP isn't complaining that Chrome has bugs, every browser has bugs. They're complaining that Chrome doesn't prioritize bug fixes unless users raise a stink. I am somewhat sympathetic, because I've worked with issue triaging, and I understand that everyone wants their issue to be #1. I am less sympathetic than I otherwise would be though because Google owns the dominant browser in the marketplace and is owned by one of the biggest companies in the world. My standards for them are higher.