Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Add Autofill support #3241

Merged
merged 10 commits into from
Aug 24, 2016
Merged

Add Autofill support #3241

merged 10 commits into from
Aug 24, 2016

Conversation

darkdh
Copy link
Member

@darkdh darkdh commented Aug 18, 2016

  • Submitted a ticket for my issue if one did not already exist.
  • Used Github auto-closing keywords in the commit message.
  • Ran git rebase -i to squash commits if needed.

fix #860

auditors: @bridiver, @bbondy

@bbondy
Copy link
Member

bbondy commented Aug 18, 2016

I think this needs a rebase pls. I'll wait to review until we have new chromium and electron builds avail.

@bridiver
Copy link
Collaborator

I don't think this is actually ready to merge yet. I'm still working with @darkdh on a few issues on the electron side and I'm pretty sure he is still working on the browser side as well.

@darkdh
Copy link
Member Author

darkdh commented Aug 19, 2016

@bridiver I just solved the locking issue in electron by brave/muon@d1991b7. And I think browser side can be reviewed for its function aspect while I'm working on making it looks better :)

email: string,
guid: Object.<string, <string>> // map of (partition, id) used to access the autofill entry in database
}],
creditCards: [{
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can't store plain text CC data in the state. It's already encrypted on the electron side so we should either store the guid and read from there or encrypt (base64 encoded) here. Preferably the former I think because we don't really need two copies.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just FYI - this is a blocker for merge because it's a major security issue

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 90f62be. Thanks.

@bridiver
Copy link
Collaborator

Can we add some tests for this? A few things that should be covered:

  1. autofill data doesn't leak from regular to private
  2. add/update and delete with good input and bad input

items.push({
label: value,
click: (item, focusedWindow) => {
ipc.send('autofill-selection-clicked', frame.get('tabId'), value, frontendId, i)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we get rid of the ipc message and do a window action here that calls webContents.autofillSelect in frames.js? Maybe track the autofill status in the frame state and show/hide the context menu based on that? Could definitely be done in a follow-up commit, but we will have to refactor the ipc eventually anyway when moving webContents mgmt to the browser process

@bbondy
Copy link
Member

bbondy commented Aug 24, 2016

@bridiver please review again but it seems like the credit card thing is resolved so I'm going to merge so we can get 0.11.6 testing in on it for the beta3 build.

@bbondy bbondy merged commit f620cf1 into master Aug 24, 2016
@luixxiul luixxiul added this to the 0.11.6dev milestone Aug 24, 2016
@darkdh darkdh mentioned this pull request Aug 24, 2016
@darkdh
Copy link
Member Author

darkdh commented Aug 24, 2016

Tests added in ec95567 and a116bbb and I will discard ipc in #3358

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Form fill (Autofill)
5 participants