Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
1Password for Safari 8.12.6 picks wrong default entry to autofill
My public domain is xxxxx.org.uk. In 1Password I have many entries for various self-hosted things all of the form:
YYY.home.xxxxx.org.uk
where YYY differs for each item. Since updating to the 8.12.6 TestFlight version of the Safari Extension (to avoid the issue where autofill does not work at all on many sites) I now find that If I am trying to log in to web page at, say:
aaa.home.xxxxx.org.uk
for which I have a dedicated 1Password entry then the extension offers as a default the entry for
qqq.home.xxxxx.org.uk
and I have to open the drop down list and manually select the correct entry.
This was never an issue previously.
3 Replies
If the passwords only apply to specific subdomains, you need to change the Autofill behavior as seen in the image below to “Only fill on this exact host”:
If that doesn’t work, you can enable only one password to autofill and have the others marked to “Never fill on this website”, but that likely won’t work very well given your scenario, so “Only fill on this exact host” is likely your best bet.
You can access this option in the menu below (example screenshot provided):
(Note that these are iOS screenshots, but it should function similarly whether you’re in Safari, the Desktop app, mobile apps, etc.)
(Sub-Note: I’m not familiar with the Testflight version of the Safari extension, so if you’re still having issues, it may be an issue with the Testflight version, NOT with standard 1Password. In that case, I recommend you submit a bug report via Testflight or directly through 1Password support.)
TestFlight is the Apple mechanism by which developers (AgileBits in this case) can distribute beta test versions of their software to the user community. The 8.12.6 version of the extension is a test version with a fix for different autofill bug.
I'm aware of the options to match the domain. My point is that prior to 8.12.6 the extension would choose the 'best match' and offer that as the default with other matches available in a drop down list. Now, in 8.12.6, it often chooses a different default and the 'best match' is typically at the top of the drop down list or alternative matches. This is (a) a behaviour change and (b) probably a bug.
