Whether it's systemic for reasons they believe internally or brazen from-the-top makes little difference. The consequences are the same.
-
-
FYI from team: "We support the 2 most recent...of Chrome, Firefox, Safari and Edge. We send this when user signs in with an old browser."
3 replies 3 retweets 17 likes -
Update from team! "As of yesterday, we have fixed the misleading interstitial and also opened up ff on linux."
3 replies 3 retweets 22 likes -
This may not be exactly what all of you want, but please do recognize that the team took some action within 24 hours of me raising this.
2 replies 0 retweets 8 likes -
As admirable as that is, it's frankly depressing you had to raise this with the team at all. They should be taking action *before* release.
1 reply 0 retweets 0 likes -
Replying to @allnutt_eu @wycats and
Personally, I'll take a team that moves quickly to correct mistakes over just about any other scenario. That's encouraging, not depressing.
1 reply 0 retweets 0 likes -
I wasn't being flippant in my opening remark, it *is* admirable. But would they have been so swift if it wasn't someone in their org asking?
2 replies 0 retweets 0 likes -
Replying to @allnutt_eu @mbleigh and
Bugs don't get fixed without advocates and bug reports. That system worked. Unsure what the issue is?
2 replies 0 retweets 1 like -
Replying to @slightlylate @mbleigh and
My impression from this & other issues is that if it works in Chrome and noone inside org complains then who cares if it's otherwise broken?
2 replies 0 retweets 1 like -
Replying to @allnutt_eu @slightlylate and
I don't think this is true at all -- the vast majority of Google products work x-browser from day one. It's not like we test only in Chrome.
3 replies 0 retweets 0 likes
Truth. But as you said it's not on the "Ready to Launch" checklist of "Google Scale Requirements". Thanks for your hard work.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.