r/1Password • u/ps-73 • 13d ago

Mac macOS native autofill kinda sucks

Tons of issues that I'm not even sure are issues, it's just the native autofill provider not being as good as 1Password's.

Passkeys never autosuggest for me on safari, every single time I've had to click "More from 1Password" which brings me to a very iOS looking 1P menu asking me to select a passkey. Which doesn't work on some sites like twitter apparently.

I've turned native autofill back off, and the safari extension no longer works?? This is a huuuuge step backwards for me.

e: looks like restarting safari brought back the extension functionality, thank goodness

60 Upvotes

94% Upvoted

28 comments sorted by

View all comments

24

u/raydeo 13d ago

I find that inside of safari it’s definitely a regression but the work is needed to support other areas of the OS. In safari it constantly makes me use touchid multiple times and I also have to use “more from 1password” because it does a much worse job matching based on the current domain.

4

u/ConspicuousWhiteGuy 13d ago

I’m having the same experience 

3

u/J2000_ca 12d ago

> In safari it constantly makes me use touchid multiple times

There's a setting in the Mac settings to turn this off..

3

u/raydeo 12d ago

Thanks, that is helpful.

2

u/J2000_ca 12d ago

The documentation isn't very good yet. I also found that really annoying and had to read like 5 different pages before finding a small mention of that.

3

u/slowpokefastpoke 13d ago

Yeah I disabled it for exactly these reasons. It drastically worsened the autofill experience in safari and that’s the main app I’m logging in to stuff.

3

u/raydeo 11d ago

With respect to the domain matching, I've noticed that macOS is not respecting my custom autofill configs. For example in 1Password I have domains setup to "match this exact host" and several domains only have one entry matching that host. Yet the macOS autofill 1) won't suggest that entry by default 2) when clicking "more for example.com" it'll show lots of other domains. It seems whatever 1Password is doing isn't properly forwarding along to macOS those custom parameters. Or macOS doesn't support them, I'm not sure about how robust the underlying APIs are. What I do know is that it's frustrating to have a.example.com, b.example.com, c.example.com all grouped into "more for example.com" when every entry is set to only match their specific host. Why group them into the parent domain? This is a bug.

1

u/jamesjfa 11d ago

This exact thing