3 ms·
Depending on the nature of the underlying bug, it would probably cause users that have their Chrome browser logged in (for configuration, history, password vaul
by shadowgovt 6y ago
Depending on the nature of the underlying bug, it would probably cause users that have their Chrome browser logged in (for configuration, history, password vault, and bookmark sharing) to be unexpectedly logged out of the browser when the cookie and local-store clearing logic fired, which is a bad UX.
Much worse UX if we're talking ChromeOS and it turns out the bug is that the logic that manages cookies and local state overlaps the logic that manages being logged into the browser-as-OS. "Navigate away from Chrome and I'm logged out of my whole computer" is no good.