4 ms·
Curious why Google requires their users to use Chrome or Firefox but can't use Safari to access Google Services when enrolled in that program? "And you will onl
by heavymark 8y ago
Curious why Google requires their users to use Chrome or Firefox but can't use Safari to access Google Services when enrolled in that program? "And you will only be able to use Chrome and Firefox to access your signed-in Google services like Gmail or Photos." I could see them just requiring Chrome but curious why they would block Safari over Firefox.
- maxerickson 8y agoSafari doesn't support the hardware.
- saagarjha 8y agoUh, what?
- maxerickson 8y agoThe Advanced Protection program requires a U2F security key. Safari doesn't support it.
- saagarjha 8y agoThanks. Hopefully this will be solved when they adopt Web Authentication?
- JetSpiegel 8y agoIf Apple doesn't come up with an alternative iAuth NIH "standard".
- saagarjha 8y agohttps://webkit.org/status/#feature-web-authentication https://webkit.org/status/#feature-web-authentication
- pcwalton 8y agoGoogle didn't support U2F for Gmail in Firefox for a long time because Chrome was incorrectly implementing the spec [1] and relied on interoperability with their previous proprietary implementation [2] of U2F, and Gmail relied on that. Apple has been a better actor in this regard than Google has, since they are planning to implement the spec as written [3]. [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1409573 https://bugzilla.mozilla.org/show_bug.cgi?id=1409573 [2]: https://bugzilla.mozilla.org/show_bug.cgi?id=1436078 https://bugzilla.mozilla.org/show_bug.cgi?id=1436078 [3]: https://webkit.org/status/#feature-web-authentication https://webkit.org/status/#feature-web-authentication
- kiallmacinnes 8y agoDidn't Google implement before the browser integration APIs spec was final? If so, I totally understand a migration period, and it's nothing to hold against them.
- pcwalton 8y agoGoogle UA sniffed on Gmail to exclude Firefox (and every browser that wasn't specifically Chrome). And there shouldn't be a "migration period" that holds the entire feature hostage until browsers implement Chrome-specific stuff.
- kiallmacinnes 8y agoMy memory was that Firefox had implemented a newer draft (or final version?) of the spec. Sniffing the UA to avoid providing broken stuff to people isn't exactly evil.