-
Notifications
You must be signed in to change notification settings - Fork 920
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
Issue 7044: Do not import cookies from Chrome and Firefox. #4121
Conversation
bbde210
to
7fc1130
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we also need to remove cookie option from importer_list.cc
which means patch for Firefox and cookies detection in ChromeImporterCanImport
for Chrome to prevent option shows up in import dialog
7fc1130
to
b0bd76c
Compare
@darkdh thanks, fixed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@bridiver please take a look |
Agreed with @tomlowenthal to do not touch BraveImporter in this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good, just checking to make sure we are ok with dropping all cookie import vs just dropping 3rd-party cookie import
Just to confirm, we are talking about dropping all cookies (first and third-party). This also came up at the Initiatives meeting where Brendan and David were of the opinion that we should just remove that functionality entirely (as opposed to disabling it by default and letting users enable it if they want) to avoid the privacy and compatibility problems we have seen with these. |
@fmarier correct- we want to remove the ability to import cookies completely 👍 (per @BrendanEich, don't even show the checkbox during manual import) |
Will try to review soon! Important to try both manual import and also import via the brave://welcome wizard |
@iefremov we got the go-ahead to remove Muon import, if you wanted to do that also 👍 Either here or in a separate PR (I'd be OK including with this one, as a distinct commit) |
b0bd76c
to
b0b67e1
Compare
Note: we do not import cookies from Safari, so nothing to disable.
b0b67e1
to
0b1a2da
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works great! Tested with both Chrome and Firefox... also tested regular import case (from settings) and then import from Wizard. Everything worked as expected 😄
@iefremov only one problem: getting unit test failure for:
I think we can delete that, push latest, and watch CI 😄 |
@bsclifton I decided to land BraveImporter removal as a follow-up, since there are too many changes involving removing patches, etc. |
All builds + tests passed; just one lint error. Gonna fix that up and merge 😄 |
Issue 7044: Do not import cookies from Chrome and Firefox.
Note: we do not import cookies from Safari, so nothing to disable.
Fix brave/brave-browser#7044
Submitter Checklist:
npm run lint
)git rebase master
(if needed).git rebase -i
to squash commits (if needed).Test Plan:
Reviewer Checklist:
After-merge Checklist:
changes has landed on.