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

Autofill - Values are vacated #3491

Closed
alexwykoff opened this issue Aug 27, 2016 · 12 comments
Closed

Autofill - Values are vacated #3491

alexwykoff opened this issue Aug 27, 2016 · 12 comments

Comments

@alexwykoff
Copy link
Contributor

Did you search for similar issues before submitting this one?
Yes

Describe the issue you encountered:
The autofill values have suddenly and mysteriously been vacated.

Expected behavior:
The autofill values should persist until intentionally deleted.

  • Platform (Win7, 8, 10? macOS? Linux distro?):
    Tested on Ubuntu. I believe it is isolated to Linux, but not 100% sure.
  • Brave Version:
    0.11.6 pre-beta5
  • Steps to reproduce:
    1. Create autofill values.
    2. ???
  • Screenshot if needed:
    screen shot 2016-08-27 at 4 56 07 pm
  • Any related issues:
@alexwykoff alexwykoff added this to the 0.11.6dev milestone Aug 27, 2016
@darkdh
Copy link
Member

darkdh commented Aug 28, 2016

Did you remove ~/Library/Application Support/brave/Web Data manually?
This will happen when you remove the database(Web Data) and the session data still keeps the guid of the entries.

@alexwykoff
Copy link
Contributor Author

I was able to repro the issue that way, however, that was not the action I took originally.

We can move this out of the milestone / close it as DNR.

@bbondy
Copy link
Member

bbondy commented Aug 29, 2016

Sounds like we need to find STR that doesn't involve clearing data, can you try to get them before closing this out @alexwykoff ?

@alexwykoff
Copy link
Contributor Author

I've fiddled with this quite a bit and cannot repro. It's a mystery.

Closing DNR

@alexwykoff
Copy link
Contributor Author

Finally found the STR:

  1. Create autofill values in a prior version (ex 0.11.6 beta6)
  2. Leave about:autofill open, quit Brave
  3. Open a newer version (ex RC1), about:autofill should open automatically

@alexwykoff alexwykoff reopened this Aug 31, 2016
@alexwykoff
Copy link
Contributor Author

Actually the STR are simpler:

  1. Create autofill values in a prior version (ex 0.11.6 beta6)
  2. Quit and reopen Brave
  3. Check about:autofill

@alexwykoff alexwykoff modified the milestones: 0.11.6dev, 1.0.0 Aug 31, 2016
@alexwykoff
Copy link
Contributor Author

autofill_vacated

@bbondy
Copy link
Member

bbondy commented Aug 31, 2016

prior version also means RC1 right?

@darkdh
Copy link
Member

darkdh commented Aug 31, 2016

STR on master with latest electron

  1. rm ~/Library/Application Support/brave
  2. npm start
  3. The database cannot be initialized error on console
  4. Any autofill changes cannot be write into disk

@darkdh darkdh self-assigned this Aug 31, 2016
@darkdh
Copy link
Member

darkdh commented Aug 31, 2016

Thanks to @bridiver ,the database initialized problem is fixed by brave/muon@18496a4.
I will add a PR for deleting non-existed entry automatically

@darkdh
Copy link
Member

darkdh commented Aug 31, 2016

QA verify steps

  1. Remove ~/Library/Application Support/brave
  2. Launch brave
  3. Add autofill data
  4. Quit brave and relaunch it
  5. The autofill data should exist

@bbondy
Copy link
Member

bbondy commented Aug 31, 2016

Fix is in brave/electron 1.3.8 also make sure electron version appears as such in about when testing. Also see Anthony's steps to test above.

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

No branches or pull requests

3 participants