Merge Form History and HTTP logins
Bug #786534 reported by
Cris Dywan
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Midori Web Browser |
Confirmed
|
Low
|
Unassigned |
Bug Description
So from a user's point of view, saved form input and saved HTTP logins are very similar, except the former can saved arbitrary fields beside the username and password.
The Clear Private Data dialogue considers it the same already.
There should be one infobar, that pops up for either form input or HTTP logins, with buttons [Remember my input] [Don't ask again] on a per-website basis
Both HTTP logins and form history should be stored in the same database. Arbitrary fields can be saved.
As recently discussed, this is a candidate for an extension that is not exposed to the user as optional, but kept separate, activated by default and disabled in private browsing mode.
description: | updated |
description: | updated |
description: | updated |
tags: | added: data |
tags: | added: password |
summary: |
- Move Form History into core and merge with HTTP logins + Merg Form History and HTTP logins |
description: | updated |
summary: |
- Merg Form History and HTTP logins + Merge Form History and HTTP logins |
tags: | added: formhistory |
To post a comment you must log in.
See bug 790935 about keyring support, which makes sense for both features.