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.11Password for Mac version: 8.11.16 (81116035 on PRODUCTION channel)Google Chrome version: 142.0.7444.601Password extension version: 8.11.16.35Additional troubleshooting information:1Password “Connect with 1Password in the browser” is checked/enabled1Password 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 bothRemoving and reinstalling the 1Password browser extensionRestarting my computer1Password Beta extension version 8.11.18.30 has the same problem

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?

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 BrowserEnter / click to AutofillCan 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.

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 issue

I agree. This is a much more thorough explanation of what I meant by...If the browser extension had a keyboard shortcut to autofill the same way with a single keystroke, this wouldn't be such an issue.

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.

Forum Discussion

jonsuh

New Contributor

2 months ago

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

browser extension

24 Replies

reub
New Contributor
2 months ago
Same issue (and same versions).
jonsuh
New Contributor
2 months ago
Not sure if this is related, but I checked the extensions’s console log, and it’s littered with these errors and warnings:
❌ Unchecked runtime.lastError: The message port closed before a response was received.
❌ Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
⚠️ background.js:80 DeviceTrust: access denied: [ missing backoffice permission, missing admin permission ] - aborting
(For the access denied warning, I checked and the extension has “Site access Allow this extension to read and change all your data on websites you visit:” set to “On all sites”)

Additional follow-up info:
CMD+\ autofill works properly with the latest versions of Mozilla Firefox (144.0.2) and 1Password browser extension (8.11.15.5)

Forum Discussion

Universal Autofill + Chrome extension not working with latest Chrome on macOS (142.0.7444.60)

24 Replies

Featured discussions

November at 1Password: the Access-Trust gap, planning your estate, and an updated unlock experience

Recent discussions

How do I prevent 1Password from autofilling on specific urls?

Safari-extension not working on self hosted app

Chrome extension breaks client side code snippet rendering

Increasing the minimum iOS version to iOS 18

Autofill not working with Chrome extension on Mac