3 ms·
I don't think the post you quoted is implying that they should've closed their eyes. It makes much more sense to try a different browser first and see if the p
by MattDaEskimo 3y ago
I don't think the post you quoted is implying that they should've closed their eyes.
It makes much more sense to try a different browser first and see if the problem persists. Instead of test versions and extensions.
- kube-system 3y agoThe post I quoted itself quoted the article saying they did test in Chromium. The article also says they tested Firefox and Safari.
- hbn 3y ago> As urgency waned because our users were using other browsers as a workaround, progress on this bug slowed to make way for other priorities. We didn’t have much left to go on without being able to reproduce the bug. However, we wanted to resolve it since users had bookmarks/settings/preferences in Chrome. We believed that we shouldn’t have to ask our users to avoid the world’s most popular browser, and we were also still getting periodic pings from various users asking whether we had made any progress on this bug.