1Password on Edge Requires Multiple CTRL+Backslash to Fill In Details?

Hi @macros,

Thank you for reporting this! This is indeed really strange and I am not able to reproduce it on my side.

Could you please try to use 1Password extension in a different browser on your computer? Do you see the same issue there?

I just tried to fill my credentials in Chromium Edge and Chrome on my PC and 1Password extension fills my credentials after unlocking without any hiccups.

Thanks!

++
Greg

This is an issue we've actually done a fair bit of work on recently, @macros. I was running into it in earlier 7.4 versions and it was fixed for me internally a few months ago. I want to say that those changes are likely in your app as well, but in digging through the various changes made here it does look like there could still be an edge case out there when your browser runs for an extended period. As such, I'd like you to give something a try for me. Next time you see 1Password locked when you're trying to fill with Ctrl + \, could you skip unlocking (just press Esc to dismiss mini – you'll need to Esc twice if you use Hello)? After that, restart your browser, then try again and let me know if filling works properly after unlocking when you do so. I'm not at all suggesting this is the way it should work (it's not), but if it does work under those circumstances, that will tell me what this issue is so I can share something a bit more actionable with our development team. Thanks!

Thanks so much for giving it a go, @macros! I think this probably means you're hitting the edge case we already know about. In short, what happens is that your browser disconnects from 1Password after running for a time and needs to be restarted (or filling needs to be triggered again) before that connection can be re-established. It should re-establish simply because you unlocked, but that's not happening right now.

I'd wager on the desktop machine you tried where it didn't seem to work that way, that might have been the result of testing so shortly after reboot. There is a ton that happens when you first unlock 1Password from actually starting up to syncing to connecting to your browser and so on. We've sped this process up a lot in 7.4, but your app is still doing a lot of work at that time. Depending on a variety of factors ranging from hardware to internet connection to how many apps you have running on boot that first fill can range from "a bit slow" to "takes long enough you think it's broken". We see less of the latter these days, but it can still happen. All the same, though, let's not place blame without evidence. Two things to try on that machine (whenever you get a chance – no rush):

1. Repeat the same test you did on the laptop the next time this happens organically on the desktop (so don't reboot right before) and see if behavior is the same.
2. Do the reboot test you did before except this time the first time you fill wait without doing anything else until you feel uncomfortable. See if it does fill eventually. Anything more than 5 seconds and I'd say you can declare it broken unless this system is particularly underpowered or startup load on that PC is particularly high. You may not be able to put a number on it, but you probably have a feel for how quick that machine generally operates on first boot so trust your own judgment on what's reasonable. Your feelings are likely accurate.

Let me know what you find. In the meantime, I'll pass along what we've already learned. I think we missed a connection between the few cases we've seen of this and the issue we left in the update where we (mostly) fixed this issue so I want to make sure I close that loop so our development team can take a closer look at it, hopefully sometime next week. :+1:

Sounds great, thanks, @macros! And yea, I'd expect that to do alright absent some pretty heavy startup load. My primary machine is my gaming rig with half of that RAM and a probably less beefy CPU (Ryzen 5 3600) and I rarely see issues on boot. That said, 1Password is about the only thing that launches on startup for me and I usually don't end up unlocking 1Password right away, so who knows. A bit more startup load and a small change in habits to unlock early and maybe I start seeing trouble. That's why I tend to rely on the machine's owner's instincts. You know your computer and your habits best and will undoubtedly be the best judge of what's reasonable and what isn't. I find that feeling trustworthy enough to skip piddling over what the machine is capable of and simply trust your judgment. :chuffed: