Forum Discussion

jonsuh's avatar
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 websi...
browser extension
1P_Dave's avatar
1P_Dave
Icon for Moderator rankModerator
2 months ago

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

Steamboater's avatar
Steamboater
Occasional Contributor
2 months ago

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

  • jonsuh's avatar
    jonsuh
    New Contributor
    2 months ago

    That 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.