Forum Discussion

Tezcatlipoca's avatar
Tezcatlipoca
Occasional Contributor
11 months ago

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...
macos
jonsuh's avatar
jonsuh
New Contributor
4 months ago

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
gloreglabert's avatar
gloreglabert
New Contributor
4 months ago

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?