What are the criteries for the fill function to work?

maxheadroom

I've got several Password entries for my different AWS accounts. They're all structured the same: account ID, username, password, MFA token. Most of them work pretty fine and autofill. There is but one which does not work. When I click on "Fill" nothings happens. I checked the entry and it looks the same to me as all the other entries in my vault that work. I can't spot the difference to figure out why it would not automatically fill the login form with the values of the entry.
What are the criteria for 1Password to fill out a web form? I guess the field names have to match and maybe the domain. Anything else?
Or is there way I can fix the entry? Worst case I'd have to recreate the entry. But I'd like to avoid this if possible.

---

1Password Version: 7.2.4
Extension Version: Not Provided
OS Version: OSX 10.14.2
Sync Type: Not Provided

rudy

@maxheadroom,

The only real criteria is that either the base domain, or the full domain matches the site that you're on. You're presumably using an item from the Login category?

Its also possible that the saved form details might be in a format that the filling code can't turn into a filling recipe, you can inspect the saved web form details by clicking on the "view saved form details" button for that particular Login item if you want to see if the field names match up with what's expected on the page.

maxheadroom

Thanks @rudy !
I've found the issue.
I noticed that in the name of the website of the entry only the string "https" was blue. Not the actual domain name as for all my other entries.
I then edited the entry and found that the Website URL had a leading blank space in front. After removing that, the FQDN was properly highlighted in blue and the auto-filling worked.

Thanks for the hint!

rudy

@maxheadroom,

That's peculiar, I'll have to take a look at that code and see if there's something we can do to improve that; I was pretty sure that we were stripping leading/trailing whitespace characters; was the whitespace before the https:// or between the https:// and the remainder of the string?

maxheadroom

It was a whitespace in front of the whole URL. So before the "htttps"

MrRooni

Thanks @maxheadroom, that will help us focus our efforts.

ref: apple-3079