You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
If a username and password are stored via Brave's internal password manager, the username is added to the 'autofill' table in brave/Web\ Data. If the user visits about:password and clears the entry, it still shows the username when the user visits the originating page.
Expected behavior:
The username should vacate from the 'autofill' table when the password is deleted. Alternatively, if a user visits about:autofill, they should be able to see and edit username values. Design consideration: If a user can globally delete all other forms of data, should they not be able to clear their usernames and passwords?
Platform (Win7, 8, 10? macOS? Linux distro?):
Tested on OS X
We plan to provide clear autocomplete data option in clear browsing data panel. And also we need to integrate the existing password manager with autofill to make the behavior normal. They've been noted in #3358
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
If a username and password are stored via Brave's internal password manager, the username is added to the 'autofill' table in brave/Web\ Data. If the user visits about:password and clears the entry, it still shows the username when the user visits the originating page.
Expected behavior:
The username should vacate from the 'autofill' table when the password is deleted. Alternatively, if a user visits about:autofill, they should be able to see and edit username values. Design consideration: If a user can globally delete all other forms of data, should they not be able to clear their usernames and passwords?
Tested on OS X
0.11.6 pre-beta6
The text was updated successfully, but these errors were encountered: