3 ms·
Having seen the source code for web browsers, I'm 100% willing to believe it's a programming error. The likeliest point of introduction is where Google added a
by shadowgovt 6y ago
Having seen the source code for web browsers, I'm 100% willing to believe it's a programming error.
The likeliest point of introduction is where Google added account login to the browser itself. At that point, either ambiguity of specification or failure to test as though the user thinks Google is a privacy-hostile agency (while using a browser that allows them to login to Google) could have resulted in someone adding a special case to refrain from throwing the credentials away that keep the browser logged in that inadvertantly failed to throw the credentials away that keep a session logged in.
- junon 6y agoWhy is something like browser identity (which is NOT a w3 standardization) at all linked with session identity?
- shadowgovt 6y agoBecause code reuse is a virtue... Until it introduces an unexpected bug.