от Daniel Dawson (Разработчик) на Апрель 15, 2011 · permalink

Hmm, 2-page login. Not something the Password Manager ever anticipated. Unfortunately, Saved Password Editor, working entirely within the design of the Password Manager, can't do a thing about that. Sorry.

от Daniel Dawson (Разработчик) на Март 17, 2011 · permalink

Works for me. You might have to edit the password in yourself, but after that, it gets filled automatically. I don't see anything required here that people don't regularly do with SPE already. What more do you want?

(Also, there's no Java on ImageShack that I know of. There's JavaScript, but that has little to do with Java, despite the name.)

If you have anything further to say on the subject, please use the support email linked in the sidebar on the details page. Thank you.

от Daniel Dawson (Разработчик) на Дек. 8, 2010 · permalink

For the record, I've already talked to Axel through other means and discussed the cause of his context menu not working. It's not anything I can change without crippling my add-on, but he can easily work around it by imitating the way Fx 4.0 does its context menu. As for reducing space consumption, he gave me a good suggestion which I will probably be implementing for the next version.

от Daniel Dawson (Разработчик) на Ноя. 20, 2010 · permalink

Okay, I see what you're talking about here; as I said before, the password manager already includes functionality for sorting on the visible fields, and Spikes never said anything about tags. That would indeed be nice. But it would indeed be more complicated than just having an interface for editing. For starters, changing the database in which the passwords are stored is probably out of the question, as it would break compatibility with anything else that interacts with that database. I'd need to store the tags separately and try to keep them reasonably in sync. New passwords wouldn't automatically be tagged in any way.

Also, no doubt you'd like to see the tags listed in the password manager and be able to filter on them (otherwise the tags aren't very useful), perhaps even see the passwords grouped in the list. That would mean significant and possibly deep changes to the password manager interface, where currently I'm only adding a few widgets to provide access to my editor.

I'll at least think about this, though.

EDIT: I've created Password Categories to provide this functionality, which isn't really appropriate as part of this add-on.

от Daniel Dawson (Разработчик) на Ноя. 17, 2010 · permalink

Well, first of all, I believe that is outside the scope of SPE. And second, the manager dialog already has sorting capability; just click on any column header to set the sorting basis. If you sort by Site, it should group together multiple accounts on any given site.

от Daniel Dawson (Разработчик) на Ноя. 4, 2010 · permalink

Thanks for your report. I will be testing before I release the next version. Note the declared compatibility: 2.0 - 2.1a3. SM 2.1b1 is not included in that range, so of course SM will refuse to allow it to be installed. Make sure you understand the difference between the declared compatibility and actual compatibility, which might well include 2.1b1; I just haven't tested it yet.

A possibility is to installed Add-on Compatibility Reporter. This will override the compatibility control and let you try out add-ons not declared compatible; you can make compatibility reports to Mozilla. I have no reason to believe SPE will not work with 2.1b1, but be warned that some truly non-working add-ons may cause you problems.

Finally, if you want to get support or make bug reports to me, please use the support link near the upper-right on the details page; reviews are not suitable for support as I have no way to contact you.

от Daniel Dawson (Разработчик) на Сен. 11, 2010 · permalink

You mean the Remove button in the Saved Passwords dialog? That's part of the built-in code, which I have not touched at all. I would suggest looking at bugzilla.mozilla.org to see if it has been reported, and if not, try to reproduce the bug (preferably on a separate profile with no vital data!) and submit a report.