Merge Form History and HTTP logins

[Cris Dywan]

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.

[Cris Dywan (kalikiana)]

See bug 790935 about keyring support, which makes sense for both features.

[André Stösel (ivaldi)]

> Both HTTP logins and form history should be stored in the same database. Arbitrary fields can be saved.

I disagree. It would be safer to store the logins in something like gnome keyring.

To make it extensible, maybe we should trigger some custom events which can override the default behaviour.

[Cris Dywan (kalikiana)]

Let me clarify: I mean the user names as well as form history other than passwords should be stored in the same database. Both HTTP login passwords and form history passwords should indeed go into the keyring.

[Cody Garver (codygarver)]

Still a bug?

[Cody Garver (codygarver)]

Yeah, still a bug, nvm.