Safari 5.1: Form Filler goes one field too far [Resolved by reserving/editing Login entry]

jpdyson

I've encountered an interesting bug in the current version of 1Password (Version 3.8.0 (build 31111) and extension 3.7). Two different websites I use regularly have three fields for login. On the first one, there's a username, password, and domain. In the past, the domain field was "remembered" via a cookie, and 1Password only filled in the username and password (which, by virtue of being a domain account, works on several other sites). Now, on this site, it overwrites the cookie-saved contents of this field with the username. I've tried deleting and re-saving the login but this does not help. It still only saves the username and password, and yet goes on to fill the domain field as well.



On the other site, the third field is called "authentication" and should be left blank for my use (I guess somebody may need it for some purpose). However, starting with the new extension (ever since it was updated to work with Safari 5.1) it has gone to fill that third field with the username, just like above.



I can't direct you to the sites where these login issues occur, because you don't have access to them. However, since the behavior is the same on both sites, and the two sites are not related (different web-based utilities, one being a Deltek time entry system and the other a Remedy web interface for tracking work requests) it seems the issue may be with the form filling routine in general, and how it handles forms with more fields to fill than data with which to fill them.



Hope this is making sense.

jpdyson

Correction/Update:



OK, I re-created logins specifically for these sites (since both use credentials that work for other sites, I had been relying on a single saved uid/pw for the primary domain on which they exist, and with no problems for years, mind you). The newly-created logins work fine.



Still worth reporting, though - why would it fill the username into a third field? Once it has filled a username field and a password field, it should stop filling.

[Deleted User]

It should actually be a bit more precise than that, once it's filled the matching fields with the details stored in 1Password it shouldn't fill any other fields. So it sounds like something wasn't matching with the saved Login and the site itself, likely because we're using a brand new filling engine that's designed to work with sites that use more than a username or password.

jpdyson

Thanks, Stu - it appears to apply to logins saved under the old engine. I actually was able to fix this - I recreated the login based on the site that was giving me trouble, and then pared down the url to just the domian. I also removed the fields that don't apply to my other sites (there was actually another field on one of them, a checkbox).



Not sure if I mentioned this before, but these were two separate domains, but for both domains, I use the same account to access several different web utilities (among other things). Now I have a single, unified item for each domain that works for every site I access with those two accounts. The only thing that seemed to change from the old ones that worked and the new ones that work is that I created it after the update.



So perhaps people will need to recreate some logins now that the new engine is in place. That's tolerable. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />

[Deleted User]

Hey jpdyson,



Thanks for updating the thread. I'm glad re-saving and paring did the trick.



I'm sure other readers will benefit from your experience.



Cheers!



Brandt