1Password autofill injecting additional characters?

Thanks Alvin_L_1P !

I've sent the site to you via email as requested.

In the meantime I wanted to fiddle with this a little bit more and the short version is I now have it working, but I have no idea how/why. Here's what I did.

I duplicated the existing site in 1Password on my Mac, changing it only to name it -Duplicate

I then edited the entry and generated a new password.

When that synced over to my iPhone, its password also showed up as all dots. Weird, but consistent, I guess?

So I then edited the entry on my iPhone, generated a new password, which of course was not all dots, and since I had left the entry open with the password revealed on my Mac, I saw that password immediately appear, looking normal.

At this point I took a little break to put my son to bed, but thinking the whole time, I wonder what happens if I log into the site with the current password from the original entry, change my password to what is in the -Duplicate entry, and see what happens if I autofill it?

So I did that. Changed the password, saved it, and logged out of the site. Went back to the login page, and selected -Duplicate.

At first, I was very worried, because when I hit the Show button on the site to show my password, it wasn't just the password with 19 dots after it - it was all dots. But I was able to login. That made no sense, so I switched from Safari to Edge, autofilled, hit Show, and the password was there normally, with no dots after it. And I was, of course, able to login.

So I'm guessing even though the site is willing to reveal my password, Safari somehow won't? I'll admit I'm stumped by that, but I'm not in the habit of revealing my password once it's been autofilled, and I'm not sure that show functionality is that common.

Aside from the difference between how Safari and Edge handle that, thought, I think this is fixed.

Like I said, though, while I can list the steps I took that resulted in this issue being fixed, I don't understand why it fixed it. But I also don't understand why it was not working in the first place.

I'm mostly just happy it is working now, and I really appreciate your fast response!