Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Universal Autofill and Quick Access aren't working in Chromium browsers like Chrome and Brave
macOS Sequoia 15.4
1Password for Mac 8.10.70
1Password extension for Edge, Version 8.10.70.27
Microsoft Edge Version 135.0.3179.54 (Official build) (arm64)
Autofill / Universal Autofi...
With the latest update of Chrome on macOS, Universal Autofill’s CMD+\ is no longer working properly with the Chrome extension.
Problem: CMD+\ does not automatically autofill form fields on any website.
Instead, you see the “Search 1Password” quick access popup, which indicates it does not detect the website you are on when you press CMD+\
- macOS version: Sequoia 15.7.1
- 1Password for Mac version: 8.11.16 (81116035 on PRODUCTION channel)
- Google Chrome version: 142.0.7444.60
- 1Password extension version: 8.11.16.35
Additional troubleshooting information:
- 1Password “Connect with 1Password in the browser” is checked/enabled
- 1Password extension “Integrate this extension with the 1Password desktop app” is enabled and “Integration status” shows “Connected 🟢”
- The following does not fix this problem:
- Quitting 1Password and Chrome, and restarting both
- Removing and reinstalling the 1Password browser extension
- Restarting my computer
- 1Password Beta extension version 8.11.18.30 has the same problem
I just want to chime in here and say that I've also been experiencing this issue, and have been going back to at least early September. I contacted customer support at that point in time, and they didn't seem to realize this was a known issue.
I echo the sentiment that this has been a pretty significant disruption. It's frustrating that it still hasn't been resolved, especially given the significant percentage of 1Password's user base that must be on Mac and using Chrome or other Chromium browsers.
At the very least, I would hope that the 1Password team would be able to offer some timeline so that its customers can have a reasonable expectation as to when this will be working normally again. But I'm not finding anything of the sort in this thread.
I've been a loyal 1Password customer for about 15 years. I may have to reconsider that loyalty if this issue persists much longer.
- 1P_Dave
Moderator
alexcr and gloreglabert
I’m really sorry for the ongoing disruption this has caused, I know how frustrating it is when things don’t work as expected. Our development team is actively investigating the issue. We’ve identified that 1Password is currently having trouble reliably collecting field information in Chromium-based browsers. This doesn’t affect non-Chromium browsers like Safari or Firefox, where the issue doesn’t occur.
Right now, we’re testing a few different approaches to improve the reliability of how we gather field data from pages opened in Chromium browsers. I’ll be sure to keep this thread updated as soon as we have any progress or new information to share. For the time being, the following workarounds exist:
- Use 1Password in the browser (the browser extension) to fill your login information into Chromium browsers instead of using Universal Autofill: Get to know 1Password in your browser
- Use a non-Chromium browser like Safari or Firefox if you'd like to continue to use Universal Autofill.
Thanks so much for your continued patience while we work on this.-Dave
1P_Dave Any feedback on the option of updating the extension to allow the same behavior to be accomplished with a single keystroke via the extension mentioned earlier in this thread? That approach should have no OS dependencies and would allow us to mimic the behavior of "Universal" autofill. From what I remember this used to be possible via the "old style" extension before universal autofill existed.
I hope you push this through, it's been many months now to hear the "Team is working on it" - just doesn't actually sound like that is true so it is hard to believe.
Thanks!
1P_Dave I hear you, but saying "it only affects Chromium-based browsers" is another way of saying that it affects ~2/3s of your customers (i.e., most of them). This isn't just an edge case affecting a few niche users.
- 1P_Dave
Just to clarify, my intention was to describe the scope of the issue and note that it was impacting Chromium-based browsers, to explain that our development team had narrowed this down to an issue with how 1Password identifies fields in those browsers. There was no intention to diminish the impact of the issue, and the word “only” wasn’t used in my message.
The internal investigation is ongoing and I'll keep this thread updated as soon as I have more to share. 🙂
-Dave
I think it's very clear that 1Password doesn't view this (or home and/or Mac users more broadly) as any kind of priority. The sole reason I'm still using 1Password at this point is inertia -- I've been a user for about the same length of time as you. I would never recommend it to anyone as a new user, and this is a perfect demonstration of why -- core functionality of the product is unreliable and effectively unmaintained.
Exactly. That's what's particularly frustrating here: This is what I think most people would consider to be "core functionality." As such, the lack or urgency in addressing this...it's just unacceptable.
