Without this field in the Defaults - unless I'm missing something really obvious - the username could never get auto-populated, unless a specific Account was pre-defined in PM.
You have very high expectations of auto-populate! biggrin.gif
I feel like i'm breaking bad news to you. There is no way for PasswordMaker to know which field in a webform is the username field without being "trained" (i.e., told in advance). I could write heuristics to try to determine it (e.g., search the <form> for a field with the word "user" or "name" and auto-populate that field), but ultimately the heuristics won't work 100% of the time.
<snip>
If you'd like me to build the heuristics I describe above, I can do that for 0.8.1... it wouldn't be too difficult. But you should set your expectations that occasionally the wrong field would get populated with your username. I suppose for these sites you could setup specific accounts if you visit them often.
Thanks for the explanation - and yes, I guess I was 'assuming' that there was some standard way of designating a username field.
I like your suggestion of heuristics, and if it isn't difficult, would love to see it added at some point in the future. Maybe you could even have the heuristics 'learn' when the User corrects a wrong guess by PM? For example, if PM makes a mistake, the User could hit a special key combo, and PM prompts for the correct field, then after the User clicks the correct field, PM fills it in then updates its heuristics? Understand, I know less than nothing about this subject, which I'm sure is pretty obvious - maybe I'm getting a little crazy here... ;)
That said, how hard would it be to allow an option to middle-click (or something) in the username field and have PM auto-pop the Default username in whatever field you click in?
Anyway, I'd still like the Username in the Defaults if for no other reason than it would be inherited by new accounts when creating them.