4 ms·
The cookies thing could be seen as a bug: the button does remove the cookies, but because your google sign in state is now tied to the browser sign in state, ne
by pilif 8y ago
The cookies thing could be seen as a bug: the button does remove the cookies, but because your google sign in state is now tied to the browser sign in state, new cookies will immediately be set.
To fix this, the “remove cookies” button would also have to sign you out of chrome which would also feel weird from a UX perspective.
All in all I think this was just released a bit early before all UX edge cases could be tackled (or even discovered. Sometimes you find things only in wider rollouts)
- cpeterso 8y agoIf exempting Google's cookies from being cleared was a bug, they would not have added a message in the UI that "you won't be signed out of your Google Account": https://twitter.com/ctavan/status/1044282084020441088 https://twitter.com/ctavan/status/1044282084020441088
- feanaro 8y ago> The cookies thing could be seen as a bug: the button does remove the cookies, but because your google sign in state is now tied to the browser sign in state, new cookies will immediately be set. Then maybe tying the Google state to the browser state was a mistake and should be reverted?