-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome/Firefox importers should not import cookies #7044
Comments
I don't think we need to import cookies. Let's just drop that. |
@tomlowenthal I assume we should still import cookies from Brave profiles? |
Updated title, per brave/brave-core#4121 (comment) |
Bumping up to P2 after recent conversations with @BrendanEich |
Verified passed with
Verification passed on
Verification PASSED on
|
Removing such a useful feature now made me not use this browser, it would take me a lot of time to log back in on all sites |
Currently, we appear to be importing all Chrome cookies into Brave when a user chooses to import cookies (presumably the same is true for Firefox and any other browsers we import from).
To avoid importing any tracking cookies, we should:
I'm not sure whether there's a way to tell third-party cookies or not, but a larger question (for @tomlowenthal) is: should we import cookies at all?
Importing legitimate login cookies does reduce the friction involved in migrating to a new browser, but perhaps migrating saved passwords is good enough to reduce the pain of having to relogin.
The text was updated successfully, but these errors were encountered: