Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Universal Autofill + Chrome extension not working with latest Chrome on macOS (142.0.7444.60)
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
24 Replies
I assume there are no updates here? It seems we're either (1) waiting on Apple to change something in macOS, (2) waiting on the dev team to patch the problem, or (3) the issue isn't sufficiently high priority for the dev team to devote real attention to. But either way, at some point it starts to feel disingenuous to advertise a "Universal Autofill" feature that doesn't work on the most popular browser platform, hasn't worked in months, and the only notice of that is buried in a community forum.
2 & 3
- 1P_Dave
Moderator
reub, gloreglabert, dndrsn, prox
I'm sorry for the continued impact that the issue is causing. Our development team's initial investigation revealed an issue with how the macOS accessibility API reports form field information from Chromium windows to the 1Password desktop app's Universal Autofill feature (Command-Backslash). We've reported this to Apple and we're currently working with our partners there to find a resolution to the issue. Universal AutoFill continues to work in non-Chromium apps.
Since the issue involves Chromium, macOS, and 1Password, I don't have an ETA on when this will be resolved. For the time being, the two best workarounds are:
- 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 Firefox if you'd like to continue to use Universal Autofill. I know that this won't be possible for most people but I wanted to mention it just in case it helps.
I'll continue to provide any updates that I can as our team works to resolve this issue together with our partners.-Dave
1Password in the browser doesn’t address the problem completely. With 1Password in the browser, it now requires 2 keystrokes/mouse clicks instead of 1 keyboard shortcut to autofill fields.
- Keyboard shortcut to open 1Password in the Browser
- Enter / click to Autofill
Can an option be added to 1Password in the browser so it behaves like Universal Autofill and autofills automatically? It should autofill automatically if there’s a login that matches the domain and only 1 login for the domain; otherwise, the browser extension popup should show with the login matches for you to choose from.
1P_Dave Given the impact of this issue and the time elapsed, would you consider offering more information for users whose experience is impaired until this is fixed? As others are noting as well, just knowing that 1Password is aware of it is neither a commitment or a timeline (even an anticipated one).
So...is this an issue that the development team is planning to actually fix? I understand that they're "aware of" the issue, but it's apparently been affecting some Chromium-based browsers for months, and that it's now been affecting all of them for several weeks. Coupled with the lack of communication and the fact that several 1Password updates have come and gone without any fix, that doesn't make me confident that it's actually ever going to be fixed.
Is there actually work in progress to get this fixed, or at what point should we assume that this is basically a dead feature that won't be coming back?
FWIW, this has been an issue with Brave for months. It started affecting Chrome more recently. This makes 1P far less useful for me. If the browser extension had a keyboard shortcut to autofill the same way with a single keystroke, this wouldn't be such an issue.
Oh, that’s not promising, but since Chrome is used by around 70% of people worldwide, I hope the 1Password team will jump on it and fix it quickly.
Adding yet another voice to the pile. This issue is wasting my time on a daily basis and the fact that it's been ongoing for over a week with no material updates is not promising...
Little update:
I've tested Microsoft Edge and Brave and there it doesn't work as in Chrome. Only magically works for me in Arc, not sure if it will helps with anything, but decided to share.
Came here to post same. CMD \ used to autofill browser forms now brings up search 1pw and wants to set main pw for Chrome app not browser.
Chrome 142.0.7444.60 (Official Build) (arm64)
- 1P_Dave
- 1P_Dave
Hello jonsuh, superuser_22, and reub! 👋
I'm sorry that Universal Autofill isn't working in Chrome. There is a known issue where Universal Autofill isn't working correctly with recent versions of Chromium. The issue affects all Chromium-based browsers including Chrome.
I've added your report to the internal work item for the issue. For the time being, as a temporary workaround, I recommend using 1Password in the browser (the browser extension) to fill your logins in Chrome by clicking on the suggestion that appears on the page rather than using the keyboard shortcut. Alternatively, non-Chromium browsers like Firefox and Safari don't experience the same issue. I'm sorry for the disruption caused.
-Dave
Issue=FS-388
It seems like Universal Autofill is what has broken Autofill in Chrome to me. I don't think this is a Chrome issue I think it's 1PW. Everything is up to date, Chrome, 1pw and extension/ CMD+\ used to fill user/pw but now just opens the app or tries to fill in the Universal PW in another Mac app.
I have tried different combinations as well. Blaming this on Chrome is not solving the issueThat might not be entirely true. If Chrome/Chromium fundamentally changed how the browser communicates with extensions, the root issue could be the browser and not the extension.
I do know it was a Chrome update that broke the functionality and not a 1Password update (it will works for versions before 142.0.7444.60), which is why I suspect it’s a browser issue.
1P_Dave Thanks for the update. I figured that was the case—I tested with Brave too, which is Chromium-based, and it has the same problem.
When you know more, a follow-up would be great, esp to know if it’s something that would be fixed with a 1Password or browser extension update; or requires a Chrome update due to a Chromium bug or change.
Same problem in the same Google Chrome version
