Form fields with # in the form name not filling out correctly
Chris
I have a site that I need to log in to for work. There's the standard username and password fields, but there's also user#2 and password#2. The password#2 field is... not the same as the password field, but the 1password browser extension (for Safari at least) treats them as the same, and fills in the password value for password#2, despite the fact that I have a separate value for that field in the site entry. It sounds like there's some incorrect parsing of form fields or the like leading to the password field being filled in the password#2 field. It should be fairly simple to reproduce, but if not I can try to create a stripped-down, anonymized version of the page I'm trying to log in to.
Comments are currently closed for this discussion. You can start a new one.
2 Posted by Jamie Phelps on 03 Feb, 2012 06:20 PM
Hi, Chris. I'm sorry for the trouble you're having. Could you send us a URL or an HTML document where we can see this in action? I haven't heard of this before (both 1Password failing on these kinds of sites and also these kinds of form naming in general), but it would not surprise me if special characters caused problems for our form filling algorithm. With a proper test case, we can make improvements to hopefully get this to work better for you.
Thanks for your patience and assistance while we work with you on this.
System closed this discussion on 07 Jun, 2012 08:25 PM.