It is fairly easy for the browser extension to find possible password fields due to them being a password type, however in general it seems to fill ALL text fields with the username hoping to get the right one if the expected field name isn't there.

Many websites seems to change or use random naming for their form fields.

I am on 1password 3 still and haven't bothered to use my free upgrade to 4 yet. I don't know if there are new browser extensions for 4 or not, so this applies to 1password 3 on mac specifically in chrome (haven't tested with other browsers yet).

When there is a hidden (type or via css:display) AND disabled text field in the form, 1password fills it with the username which breaks the functionality of many sites that rely on hidden form fields. It would seem logical that if a field is hidden and disabled, that it probably isn't the username field and shouldn't be modified?

The bank has a nice little bit of javascript in the page as well to validate that the login form is only submitted once per pageview. Of course because 1password put my userId in the hidden/disabled text field, I get the alert popup and no login.

Comments

We've seen several users reporting difficulty with form-filling on the website you mention, and our tech gurus are working hard to find a way to make form-filling better and more automatic with this and other sites.

Thanks so much for providing that detailed feedback, it has been passed along

Form-filling improvements is something that is always on our to-do list. Unfortunately I can't say anything specific about when we'll be able to solve the riddle of this particular site. We really appreciate your patience as we work to improve 1Password's filling performance.

So I got an update from support that indicated this problem has been fixed in 1password 4. It sounds like they don't plan to patch this in 1password 3. Support suggested that the "fix" for this issue was for me to pay for an upgrade to 1password 4.

I understand not wanting to maintain old code and having the dev team busy with the new version. However as a consumer 1password 3 works perfect for me aside from this one issue. I only purchased July of last year...so already being forced into a paid upgrade already doesn't make me feel very good.

I'm so sorry if you are feeling forced into an upgrade. That is certainly not our intent. There are, however, a few factors that come into play here. We are a small company, and our developers are mostly focussed (as you say) on polishing some features and squashing some bugs in 1Password 4. This doesn't mean that we are ignoring 1Password 3, but time constraints do factor in - there's just not always enough hours in the day to do all that we would like to do! And we would love to patch up 1Password 3, but unfortunately because the extension has been completely re-written in version 4 (in part to get around problems like this!), it's not a simple matter of adding the new code to the existing extension.

I hope this helps to understand the situation a bit better. I know it's not a perfect answer, but we will do our best to add fixes to 1Password 3 when it is possible.

I'm sorry that you're having difficulty with the filling feature in 1Password 4. Are you having this trouble with any websites in particular? As I've mentioned previously, this is something our tech gurus are committed to improving, and the more information we have about the situation, the better. If you could provide us with some websites that aren't filling correctly, we'd love to do some testing on our end.

Thanks so much for including your workaround here. I do apologize that you have found it necessary! If there are any specific sites that are doing badly here, while I can't promise immediate progress, if you let us know which sites you are having this trouble on, I will file it with our filling gurus to see if they can't improve 1Password's behaviour on such sites in the future.

Thanks for confirming that for me! I'm sorry if I misunderstood your original post. Unfortunately I have no updates right now on this particular site. If we can improve 1Password's behaviour here, we'll be sure to let you know!

Thanks so much for including the link! Our tech gurus are aware of the issue with this site, and they are looking into ways to make 1Password's behaviour here better. Unfortunately, I can't promise anything, but we'll do our best.

Can we get some proper feedback on this, rather than "sorry, we're working on stuff to improve, but can't promise anything"?
This issue is really annoying and defeats the purpose of having a single password, if I have to remember different passwords for the websites that HAPPEN not to work.

Unfortunately, banking sites can often be tricky to test for us here. Without an actual account, we have to fill in dummy information, so we never actually see a successful result (we can't actually log in using "test123" as a username and password!) This sometimes makes it difficult to pin down where the error is coming in. In this case, I've just spoken with one of our form-filling gurus, and he is unable to reproduce the error. If we can't see it, it's a lot harder to fix.

That being said, I'm wondering if you can help me with a bit of a test. First of all, I'm curious: have you tried using MikeT's suggested steps? If not, please see if a Login created like so behaves any better. Additionally, please try disabling auto-submit. Does the entry fill correctly if you do not ask it to submit?

I do apologize for the inconvenience here. I know how great it is to have 1Password fill in sites automatically, and I grumble slightly under my breath every time I have to copy and paste a password manually. I wish I had a better answer for you - please let me know if submit helps things behave a bit better!

1. Test failed login w/o 1password:
- enter by hand: user: foo pass: bar
---> u ll get a response from the server
2. Test autofill but not auto-submit foo/bar with a prepared 1password entry:
- create an entry for the dkb.de site in 1password user: foo pass: bar
- set auto-submit:OFF in that profile
- open the url https://banking.dkb.de/portal/portal
- fill creds with 1password extension
- submit by clicking the login btn "Anmelden"
---> u ll get no response from the server, but a javascript method
creates a div with a message "Ihre Daten wurden bereits
abgesendet!"
translation: "Your data has already been sent!" .
This is a misguiding message, cause the data actually has
not been send. The devs of that site made a mistake here.
expected: same behavior like Test 1

Note: same happens with auto-submit:ON

The test should be enough to reproduce the issue. Also reread carefully what the OP @matp posted. I think his Suggestion could be the correct solution.

Anyway, I could fix the site for my personal use, with the help of a local greasemonkey userscript, which disables that stupid javascript-check on that site. But a general solution might be @matp's suggestion. Please use my TEST to verify his suggestion.

Thanks so much for adding your two-cents here! I'll pass this along to our filling gurus (I'll admit, I'm not a developer, so my understanding of html and javascript is still very basic.) But since, as you say, it is likely that the web developers made a mistake (or did things in a unique way) when coding the site, we might not be able to get 1Password to behave properly here.

For the time being, this is just one of those websites where you'll have to copy and paste your user information from 1Password into the fields manually.

I really do wish that I had a better answer for you all - your time in testing is much appreciated, and we will update you here if we are able to make any progress on this issue!

@Megan, let me rewrite. That javascript message is actually not a mistake of the dkb-devs. They could not know (test) that somebody tries to fill in the form values automatically. The message they produce is correct for the case they had in mind.

Anyway, and don't take me wrong, it would be nice to read some opinion of your 1Password filling guru on the suggestion of @matp. I am pretty sure agilebits can get 1Password behave properly on that site.

Hi, guys. I work on the browser extensions quite a bit, and I recently made a change that I think should help with this issue with filling fields that are not visible to the user. (Please note I say not visible rather than hidden since <input type="hidden"> is an actual HTML construct, and I don't want to confuse things here by mixing up our terminology.) I made the change for 1Password 4 extension. Our code has diverged quite a bit since 1Password 4's release, so I will need to manually migrate this change over to 1Password 3 at some point.

Could you give the latest 1Password 4 extension a try and let me know if you still have trouble with it filling these non-visible fields?

Thanks @jxpx777, I've tried the latest 1Password 4 browser extension, and the beta browser extension too, but the same issue occurs. Here's a video showing an end-to-end test, including creating a login in 1Password. It's only 40s long but show's how to easily reproduce the issue even without banking credentials. https://www.dropbox.com/s/h7xhq9vppg2f5cn/dkb1password.mp4

Here's a vimeo version, but that's still encoding and won't be viewable for about 30mins:

Looking at that video, I have to correct my description of the TEST I proposed. In Test2 hitting the submit btn does not create a div. As we see in @io41's video, it is an alert box. I thought it was a div, cause I used Firefox, which displays alert boxes that look like overlay divs.

@Russell_Stout@jxpx777 sorry, I did not see an uploaded version here so I presumed it was the latest beta on the official download page. In the video above I tested on the latest stable release (4.0.1) and the current beta, which was at version 4.1.0.b2. Both had the same behaviour.

I've narrowed down the code that's being triggered on the site, but so far I haven't been able to figure out where it's being triggered from 1Password's filling algorithm. I'll investigate more and see what I can find.

@io41: With uploaded I did not mean he uploaded it here. He uploaded to the server(s), that deliver the extensions. You should go into Safari-->Settings-->Extensions and see if there is an update available for the 1Password extension. And write down the version number you read there after you eventually updated the extension there.

Hi, guys. I found the issue and pushed a fix for review, but I expect there to be some internal discussion and debate about it as it makes a pretty significant change to our core filling algorithm. It might be a little while before the solution is available in a release, but I wanted to update you all with the latest information since you've been so helpful in getting to the bottom of it. Thanks for your patience!

@jxpx777 that's a mil for all the effort, the feedback and keeping us in the loop. Also, wooohoo! :-) I realise code & architecture reviews can take quite some time but it's great to see it's getting all this attention.