Hi Eric,
Thanks a lot for a great extension. I've read a LOT of the help available on the website, but I'm still having problems understanding how the URL matching algorithm works, and I find other aspects of the interface quite confusing. This long post is not a rant or complaint, I just want to help you make a great extension even better :-)
For example, I want to apply a modifier to multiple subdomains of the same domain:
subdomain1.mydomain.com
subdomain2.mydomain.com
etc. regardless of the protocol/port/path/anchor/query. I have been testing with 1.6.1. I thought it would be enough to create an account with the name 'mydomain.com' which had the modifier set, but this never matched - all subdomains used the default settings. I also set 'Use the following URL to calculate the generated password' to 'mydomain.com' but this didn't help either. It's not clear to me which one is supposed to be used in the matching process - 'Name' sounds like it's just a label, and 'Use the following URL to calculate the generated password' sounds like it only affects calculation (not matching) of the current browser URL with this account.
The only way I ever could get it to match and apply the modifier was by explicitly adding a regexp pattern:
https?://[^/]+\.mydomain\.com/.*
to the pattern list entitled 'Activate auto-population when the URL of a webpage matches any of the following patterns', even though I don't want auto-population to occur! I only want population when I press the CoolKey (i.e. non-automatic - I suggest you change the sentence above it to read "Population can also activated using CoolKey", since it's confusing to say that *automatic* population can be activated *manually*).
Anyway, I hope you will say that this is a bug in the matching logic, because it would be deeply inconvenient to have to create a wildcard or regexp for every single account I create.
Nor was it clear to me whether the pattern list controlled whether population was automatic for only the extra fields in "Advanced Auto-Populate", or also for the username/password fields. What is supposed to happen if 'Automatically populate username and password fields for sites that match this URL' is unchecked, but one of the wildcards/regexps matches this URL? The wording suggests that in this case username/password fields will be automatically populated.
Furthermore, there really need to be at least two pattern lists per account, not just one. Why? Because there needs to be one to determine whether the account matches the current browser URL or not (and hence whether the account's settings should be applied), and then one to decide whether population of the custom fields in 'Advanced Auto-Populate' is automatic or not, so that for example, from a single account you could have manual population (CoolKey only) of
http://subdomain1.mydomain.com/login http://subdomain2.mydomain.com/login http://myotherdomain.com/loginbut automatic population of
http://subdomain3.mydomain.com/specific/pa...rofile-settingsusing custom fields (for phone number, address etc.)
If two pattern lists is asking too much, please bear in mind that URL matching the account is more important than controlling automatic/manual population, so the pattern list should affect matching. You could easily move the automatic/manual population to be an option available in each custom field.
(In a perfect world you could even have multiple sets of custom fields per account, but that's probably going too far.)
Hope this is useful. If you fixed the matching bug, improved the wording in the dialog boxes, and made a better distinction between options which control matching vs. options which control automatic/manual, you'd be well on the way to a perfect extension :-)
Thanks,
Adam