Rated 5 out of 5 stars

I've having semi-success with this extension. Three scenarios... (1) some sites it's not offering any password assistance, (2) some sites it's only using the previousy-stored password prior to me installing this extension, and (3) other sites it's working perfectly.

Is the extension choosy about the hostname for a site? I'm having trouble with .ca domains, for example, but not .org.

UPDATE - It seems that Keychain access was not granted to Firefox until after a relaunch (a second time). As soon as I launched it again and visited the login form, it prompted me for Keychain access and then auto-fill worked correctly. Thanks. :)

This review is for a previous version of the add-on (1.1.8.1-signed.1-signed). 

It sounds more likely that some of the sites your'e visiting have disabled autocompletion on their password fields. Firefox honours that request, so the extension has very little involvement in any of that, basically just doing what it's told (or not doing what it's not told in this case). There may be some differences between browser choices here, but you could compare behaviour in Safari or Chrome - do they offer to store passwords for those sites?

Also, I have to jump through some hoops to try to work with passwords stored by Chrome and Safari, so it could also be that there's still some funny behaviour there if you've saved passwords for some of the problematic sites in another browser...

No special logic based on domain names.