I think this is referring to the FedCM api [1]

It works with providers other than Google, just no one else has implemented it yet. Google's One Tap library tries to use the new api, and falls back to the classic One Tap popup when using a browser that doesn't yet implement FedCM (notice how the chrome built-in one says "sign in with google.com" rather than "sign in with Google" like One Tap normally shows)

Mozilla are working on implementing it, but it's a pretty complex system so it'll take time. I presume Safari will as well if it gets popular enough

[1]: https://developer.mozilla.org/en-US/docs/Web/API/FedCM_API

▲

mooreds 5 days ago | parent | next [-]

Yeah, I attend the FedCM meetings. Firefox has one dev working on it who attends regularly. I have found some posts where the safari team has said "seems like a good idea, we'll consider implementing" but have not seen further action.

Edge supports it, and it should be relatively easy for the other Chromium based browsers.

	▲	captn3m0 5 days ago \| parent [-]
		- https://github.com/WebKit/standards-positions/issues/309 - https://github.com/mozilla/standards-positions/issues/618

▲

kro 5 days ago | parent | prev [-]

What is there to fallback to I wonder - 3rd party cookies should be deprecated/blocked by now, so how can the gsi script retrieve google session information?