Warum wurde "Saved Password Editor" geschaffen?
I had tried one of those "bookmarklets" (a bookmark consisting of a small script) that is supposed to disable the "autocomplete=no" that appears in some forms and allow the passwords entered there to be saved, but I found it didn't always work—some sites apparently worked around it some way or other. For others, Firefox does offer to save it, but the page quickly redirects and the notification bar disappears before you notice it (which might ot might not be true with newer Firefox versions), let alone are able to do anything with it.
I decided that if you can't defeat these pages directly, you can work around them in a place they can't interfere: as an add-on. Of course, I didn't want just a quick-and-dirty solution like the bookmarklet provided, but something that can find other applications. In other words, whatever reason you might have for editing your saved passwords, this add-on should be useful.
Was kommt als nächstes für Saved Password Editor
As of late August 2016, I am releasing a multiprocess-compatible version. However, it is still not restartless. I may try to change that next; however, it will probably stay as an overlay extension for right now, as I am not sure whether the Add-on SDK supports what SPE does well. Eventually, I need to convert it away from being an overlay extension, as those are being phased out; I would consider releasing that as a new extension, and keep the old one for those cases where newer types are not supported, if there are any. Ultimately, WebExtensions are supposed to be the future, but the API is not nearly complete enough for my needs right now.
Über den Entwickler
|Benutzer seit||July 26, 2008|
|Anzahl der entwickelten Add-ons||4 Add-ons|
|Durchschnittliche Bewertung der Add-ons des Entwicklers||Bewertet mit 5 von 5 Sternen|