I think there is benefit to this because folding some identity primitives into the browser helps the user (in UX, in security). This was certainly true of password managers.
The other comments talk about how you will need to have a fallback. That is certainly true. But just because you have to have a fallback doesn't mean you can't improve things.
> Every web application nowadays send you a welcome, onboarding, reminder after the verification. (No user privacy enhancement)
But would they need to if they could trust info coming from the browser?
I think there is benefit to this because folding some identity primitives into the browser helps the user (in UX, in security). This was certainly true of password managers.
The other comments talk about how you will need to have a fallback. That is certainly true. But just because you have to have a fallback doesn't mean you can't improve things.
> Every web application nowadays send you a welcome, onboarding, reminder after the verification. (No user privacy enhancement)
But would they need to if they could trust info coming from the browser?
0: I wrote an intro to this here: https://www.infoq.com/articles/federated-credentials-managem...