@Username13 thanks, it’s a confirmation. If you didn’t notice, each of those flags were testing parts of what Brave does to randomize device information, place cookies into ephemeral storage, etc. Basically just kind of taking down parts of Brave’s privacy protections to see if that was part.
I’ve only seen like 3 people say they have specifically tried the flags so far and they have said it didn’t work. And I have also seen some people try across multiple devices but this issue only impacts one.
So far it doesn’t seem specific to any Brave version, OS, Shields, cookies settings, etc. And if we consider other reports I had found of it happening on other devices, it may just purely be a Google thing. But if so, not sure what it is they are looking at and having triggered.
People with the problem, please keep brave://flags/#enable-bound-session-credentials enabled and on logout event please open brave://histograms/Signin.BoundSessionCredentials and dump everything you got on this page here. I’m mostly curious if anyone of you got Signin.BoundSessionCredentials.SessionTerminationTrigger histogram and what the value it has in this case.
The flag they mentioned is one that person said they disabled and the issue went away. But let’s not mess with that flag. The focus here is the Histogram for those of you being logged out.
I’d ask that you provide the Histogram data as a reply on the Github if possible. If you can’t or don’t want to do it there, advise and we can look at another way.
Yes if anyone wants to submit their histogram information but doesn’t have a Github account (or doesn’t want to post it publicly) please let me know and we can do this via DM.
Hi all, we’ve released a fix in Nightly channel. Is anyone here using Nightly, and can confirm that they’re no longer experiencing this? Thanks in advance! Once we begin to receive confirmations we will move it up to additional release channels.
