How do I disable form autosubmit?

Adding another +1 to this (both the option to globally disable as well as a by-item option)

My guess is that many, or even most, of the people posting in this thread are using Safari. After doing some digging, it looks like this is a combination of a few different issues.

1. As discussed in https://1password.community/discussion/129350/since-upgrading-to-1pw8-1pw-safari-extension-no-longer-works-or-even-exists, for some reason part of the Safari extension often doesn't get registered correctly in the system. Anecdotally, it often seems to un-register during a browsing session, requiring me to run lsregister -f -R /Applications/Safari.app or sometimes even lsregister -f -R /Applications/1Password\ for\ Safari.app even when it worked just moments earlier.
2. The keyboard shortcuts for the new Safari extension https://1password.community/discussion/129706/prevent-1password-safari-extension-from-using-command-shift-x. As such, it responds to Cmd+Shift+X and not Cmd+\.
3. 1Password's new global autofill functionality likes to be helpful. As a result, pressing Cmd+\ is caught by 1Password and https://1password.community/discussion/129376/1password-for-safari-extension-animated-slow-filling.

To break it down further, something along these lines is happening:

1. User presses Cmd+\
2. 1Password app intercepts the shortcut
3. 1Password app determines that the active app is Safari, identifies active site
4. User selects which login item to use
5. (Unconfirmed speculation on my part) 1Password app attempts to communicate this with Safari extension, but fails
6. 1Password app, falling back to global autofill, injects keystrokes of the username, tab, the password, and return

Thanks for the clarification, billj. Understood, and appreciated. 👍

billj I got used to manually submitting with 1P 7, but since changing to 8 last week, it has been kinda nice to let it auto-submit (when it works).

Thank you 1P_PeterG . Just to clarify: My preference -- to be able to globally disable autosubmit -- seems to be what everyone in this thread is asking for, except @bcometa who apparently likes autosubmit and wants to disable it only when it breaks the login process.

I'm with Michael Fey, who said in his previously referenced blog post, "We feel strongly that removing the ability to automatically submit passwords is the right call."

But I'd be happy with a setting to globally disable it.

Hi billj, thanks for this request. I get where you're coming from! While I can't speak at this point to how the implementation of this feature might be done, we do appreciate knowing about your use case, and will definitely be keeping this kind of scenario in mind. Thank you for sharing the specifics with us.

I already cast my vote in favor of being able to disable autosubmit. But if the proposal by @bcometa (disable autosubmit on a per-site basis) were implemented, I would need to disable autosubmit over six hundred times. Because I don't want to use autosubmit at all, and I have over 600 login items.

Of course, there could be a toggle on each login item to individually override whatever the global state is, but that's likely asking too much of the team.

Without the ability to globally disable autosubmit, disabling it on a per-site basis would not be ideal at all.

Hi folks! Thanks for your discussion here. 😃

@natevancouver - thanks for pointing this out. My last reply did contain an inadvertent conflation of terms.

To be clear: the issue submitted (and for which we're now tallying votes) is for a disable autosubmit, not autofill option. So the request itself was always accurate to your intent, my post just didn't completely reflect that. Again, thanks for checking!

And I will now submit votes on behalf of everyone who has requested from May 6 forward! 👍

Vote for me too. Auto-fill breaks Wells Fargo for me. Disabling on a per-site basis would be ideal since it works everywhere else.

Adding my vote to this too, for all the reasons already stated. I was surprised to see this behavior changed, as I remember the post that @natevancouver referenced above.

On a related note, it feels like a lot of product behavior history has been overwritten with v8. I get that this is pretty much a ground up rewrite, but as someone who's read the release notes over the years and seen all the care put into tweaking all kinds of small interactions, it's really frustrating to see years of good work thrown in the bin.