Auto-submit coming to X?

jcwacky

Are there plans to bring Auto-submit to 1Password X? It seems that currently it only automatically fills in the username and password, and you still have to manually click "Log In" or press enter. For me, this is a step backwards.

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

c_shaw

Hi @jcwacky,

In a future release we'll take this further and allow you to automatically fill as well.

Taken from https://discussions.agilebits.com/discussion/comment/400854/#Comment_400854

dteare

Autosubmit is trickier than you might imagine it to be :)

There's a rather famous (to us anyway) Bugzilla bug report that needs to be moved forward before 1Password X would be able to perform autosubmit without the help of a desktop client.

So while this is something I'm very interested in adding, it will be quite some time until we're able to do so. In the interim we try to do our best to leave focus within the correct field after filling so you're able to simply press enter to continue. As a keyboard user I don't mind this too much as long as I never need to lift my hands off the keys to get to the trackpad :)

neal007

Make this an option if it comes back as now I have the opportunity to check "remember me" on some logins that I couldn't before. But for the most part I do want auto submit as well.

beyer

@neal007: We've provided an option for most apps in the past, so it's very likely we will here as well. :) :+1:

--
Andrew Beyer (Ann Arbor, MI)
Lifeline @ AgileBits

kildarr

Why would you remove auto-submit when is worked in the previous extension?

dteare

That's a great question, @kildarr! Let's see if I can give an equally great answer. 🙂

First things first, we didn't remove anything from 1Password X. While one could argue that it was possible in 1Password, 1Password X has been recreated from the ground up to run completely within your browser. It means we cannot rely on the main application to do things for us, which was the case here. When using the 1Password extension when filling a website, the extension would perform the filling and leave the focus in the password field. It would then send a I'm done! message back to the main app which would then us a native OS api to press the Enter key for us. It was a round about solution but it worked quite well.

In the case of 1Password X we simply can't perform Autosubmit. We'd love to "press" the Enter key for you but the aforementioned Bugzilla issue is blocking us from doing so. With any luck that will be addressed in the future and we can add Autosubmit to 1Password X. Until then we do our best to leave the focus on the password field for you so you only need to press the Enter key after filling.

I hope that helps clear things up. Please let me know and I'll be happy to natter on more if needed. 🙂

++dave;

Dr_T

Dave: Your level of customer support is amazing. This is the kind of thing that makes users want to stick with 1P when other password managers are available. Keep up the good work!

dteare

Thank you, @Dr_T! ❤️🤗😘

Paalo Bisgaard

I google'd about auto-submit on 1P X and found this thread - happy to see an explanation instead of "yeah, in some time we might add it" kind of comment... thanks Dave!

beyer

@Paalo Bisgaard: On behalf of Dave, you're very welcome!

I learn from almost every one of Dave's posts both from the technical details and how best to treat (in actuality love) folks who use 1Password! 💙

Dave is one of the few leaders I've known that indeed leads by example and he honestly wouldn't be able to do that without customers like yourself. For that I wholeheartedly thank you! 🤗

&drew

loilo

English is not my first language, so please forgive me if this comes over in a know-it-all manner — but I'd be very curious what prevents the extension from calling submit() on the surrounding <form> instead of simulating an Enter press? That should at least work 99.9% of the time. :)

jxpx777

Hi, @loilo! In a perfect world, yes, calling submit on the form would suffice. It seems so simple, doesn't it? Unfortunately, a large number of sites (I'm not sure I would say "most sites", but enough sites that it causes unacceptable success rates.) simply do not have good semantic markup for their forms or handle the submit event in unexpected or nonstandard ways.

What we have found over the years is that many websites either do not respond properly when the form is submitted or they require some other sort of interaction for submitting. For instance, perhaps there's a button-like¹ element that has to be clicked and when the user clicks it, it actually stops the normal submit event from firing (via something like preventDefault or simply return false;). Other times, the site hasn't covered all angles from which a form might be submitted and this causes the site to have an error. When this happens, users think it's 1Password that is not working properly and this causes confusion for all involved.

We used to have an algorithm that we called "clicky submit", which was our best effort to trigger the site to proceed with the form via Javascript. It employed many different tricks and had a lot of things that it attempted to do starting with simply submitting the form and then progressively trying more and more exotic approaches until, as far as the script could tell, the page responded in a way that looked like the submit had occurred. On most sites, this would mean navigating to a new page, but in some single-page applications, the sign in form is removed from the page and replaced with the app's content without a page load occurring, so we had to monitor the page for changes to its structure as well. Overall, we found "clicky submit" to be so unreliable and the web to have so many edge cases that we decided that submit would only be done by natively simulating the keystroke return in a password field. Some sites still do not accept this as a method for submitting their forms, but at least when this is the case, we can easily explain why the submit did not occur.

I hope this makes sense. Please do let us know if you have other questions!

--
Jamie Phelps
Code Wrangler @ 1Password
Fort Worth, Texas

P.S. Your English is fine. :smile:

---

1. It might be a proper <input type="button">, <button>, or <input type="submit"> but it might also be a <a> link or maybe even just an <img> or <div>. We've seen all kinds! ↩︎

loilo

I thought it was something like that, but I didn't anticipate it to be so widespread (which is exactly what I was curious about since I'm certainly confident in you folks being able to submit a regular form ;) ). Thanks for going so deep on that! :)

jxpx777

My pleasure! :+1:

majelbstoat

Can't you make it use the desktop app if it's available, to do the same thing? I log in to services all day long and X is a big step back for me because of this. What's worse is that it no longer appears to work even if I go back to the old extension when used with 1Password 7.

I was briefly annoyed that I was forced to download 1Password 7 for a new machine when I've been happily been a paid user of 6 for a long time, then have to deal with the constant nags. So sure, I buy a subscription, because fair's fair and it works well, but now there's reduced functionality too? Not great, even though I'm sympathetic to the technical reasons.

AGAlumB

Can't you make it use the desktop app if it's available, to do the same thing? I log in to services all day long and X is a big step back for me because of this. What's worse is that it no longer appears to work even if I go back to the old extension when used with 1Password 7.

@majelbstoat: It isn't currently possible to make use of the native apps with 1Password X. And, as Dave mentioned, 1Password X was designed expressly to work on its own. But perhaps that's something we could do in the future. :)

I was briefly annoyed that I was forced to download 1Password 7 for a new machine when I've been happily been a paid user of 6 for a long time, then have to deal with the constant nags. So sure, I buy a subscription, because fair's fair and it works well, but now there's reduced functionality too? Not great, even though I'm sympathetic to the technical reasons.

I don't follow you here. 1Password 7 isn't a forced upgrade. If you want to keep using 1Password 6, that's totally fine! And 1Password X is completely separate, so it won't affect the desktop extension. And either works with a 1Password.com membership. It sounds like you may just need to toggle "Automatically sign in" in 1Password for Mac Preferences > Browsers. Let me know either way! :)

majelbstoat

It was a new machine, and 1Password 6 was no longer available. I'm back to the old extension for now, with Automatically Sign In, which seems to be doing the trick in the interim. Thanks for the pointer :)

AGAlumB

Sure thing! We're here if you need us. have a great weekend. :)

akano

An interim solution request:

After filling a form, focus one of the elements of the form it filled. The user can then just hit enter themselves to submit, instead of having to go back to the mouse (or press Tab two dozen times, then enter).

AGAlumB

@akano: In my experience, 1Password does just that: leaves the password field focused so it's easy to submit the form. If you're not seeing that, it would be helpful to have some basic information: OS, 1Password, and browser versions, along with the URL where you're having trouble. Thanks in advance!

akano

@brenty: ArchLinux, Firefox 62.0, 1P X 1.10.3, https://discussions.agilebits.com/entry/signin - use the hotkey to open 1p, hit enter to fill the site, and.... no focus.

AGAlumB

@akano: I'm not sure we're on the same page here. It is impossible for there to be no focus, unless there's some bizarre OS-level issue. This is what happens when I use 1Password X to fill:

Note the cursor in the password field. If you are seeing that but the browser window/tab/whatever is not actually active, I'm not sure what to tell you. The only thing 1Password X can do is fill the fields and leave the cursor at the end. Anything outside of the browser, such as something else affecting what is active in the UI, is not something we can control unfortunately. :(

tc1p

I know that what is holding autosubmit back for 1PasswordX is the webkit bug, but in the interim since it looks like it's never going to get fixed (last update was 3 years ago...) could you offer the ability for 1PasswordX to integrate with the Desktop app for Windows like it does on Mac? Autosubmit is a big deal for me, but I prefer the look of 1PasswordX, its additional password generation capabilities, and the 1PasswordX icon in the form field.

AGAlumB

@tc1p: Ah, I'd long forgotten about that even. Much more recently (last year), Apple made it clear that this sort of functionality is not acceptable in Safari going forward, and apps in general are discouraged from sending keystrokes on macOS, since that's easily abused. I suspect it will be actively prevented in the future, though at this point it's more of a platform guideline. That's why 1Password for Mac version 7 does not support autosubmit at all. And, frankly, it was unreliable in many cases and also had unintended consequences in others (often due to "creative" website design), so I can't say it's something I personally miss. More often than not, we needed to tell users how to disable it to work around issues like that, or deal with CAPTCHAs, which are fairly common these days. Suffice to say I don't see it making a comeback.

It's also not feasible for 1Password X to do it anyway, as it operates entirely in the browser and simply cannot send keystrokes. We are working on desktop app integration between 1Password X and 1Password for Mac though, which will allow for some other benefits there. In either case, on most sites, 1Password can leave leave the password field focused after filling, so that it's just a matter of hitting Return to submit the form. Cheers! :)