Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
Forum Discussion
Tomb73
1 month agoNew Contributor
Autofill on Hilton website stopped?
Have been 1password user for a very long time. For some reason, it stopped filling in the user/pw on hilton.com. Other sites still work fine. Am using Firefox 148.02 on MacOS Tahoe 26.2. An...
- 5 days ago
OK, so have been struggling with this for a while. Then, in Firefox, some web pages were not formatting properly. In searching for possible issues, it was suggested that clearing cache files. Tried that, and it fixed the 'formatting' problem, but also seems to have eliminated the 1password issue... Will likely add this to my 'normal' maintenance routine....
Tomb73
1 month agoNew Contributor
Thanks, Chris, tried that. No joy. Then I deleted the login for Hilton, and recreated it, but 1password still does nothing. When I click on the userid or pw boxes, I get the drop down with my login, but clicking on it does not populate the login box... Sigh. You can see the 1Password icon in the password box, and it seems to recognize the login it has stored, but will not put it into the fields.
- 1P_Gem1 month ago
Moderator
Hi Tomb73, thanks for your reply!
I've done some testing on my end, and so far I'm seeing the same result as my colleague Chris - everything is filling normally. I'd also like to note that I've redacted the screenshot you included, as it contained some login information.
Could you follow the steps below for me:
- Right click on the 1Password icon in your browser toolbar, and click Settings.
- Click About.
- Let us know which extension version is listed there.
I look forward to hearing from you!
- Tomb731 month agoNew Contributor
It shows
and another symptom. If I click on the 'save to 1password' button on the hilton login screen after I manually enter user/pw, get:
Very strange as it only happens (to date) on hilton.com.
- 1P_Gem1 month ago
Moderator
Hi Tomb73, thanks for getting back to me with this information!
I've now been able to reproduce this on my end as well. It turns out I couldn't reproduce it previously because I was using the Beta version of the extension in Firefox. As soon as I switched to the version you're using, the issue appeared.
Would you be willing to try the Beta version and let me know if it behaves normally there? You'll need to disable your current version to avoid any overlap:
I look forward to hearing from you!