Skip to main content
I
IainMcc
November 1, 2024
Question

Hide On This Page remains non-persistent, and local to one single url.

  • November 1, 2024
  • 1 reply
  • 81 views

So, I'm doing dev work on a web app.

The 1Password thingy obscures parts of input fields that I want unobscured for testing purposes (end users, if they have 1Password, will be happy to use autofill). So I right click and select "Hide on this page".

Problem one is, this request is per-url. If I go to another page in the app, the widget is there on any field that 1Password thinks might be an autofill candidate. I have also seen the request not apply to the same url when a query string changes.

Problem two is, this request is very temporary. 1Password stops honoring it after a random amount of time, and definitely ignores the request thereafter when I load a new build of the app (restart the Tomcat container, which pulls in the new .war files on boot). Or if I hit Ctrl-F5.

I've seen requests dating back to 2021 asking for this almost-feature to be promoted to actual-feature - that is, having a settings item listing urls (including wildcards) to not do autofill on.

That would be nice, if I could say "don't do autofill on https://localhost/my-app/*" and have that stick.

Is there any plan at all to do this?

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided

1 reply

1P_Dave
1P_Dave
1Password Employee
November 4, 2024

Hello @iainmac! 👋

Thanks for reaching out! The team was able to share some good news recently regarding this feature request in our Reddit AMA:

You did however catch me at a good time because in the coming weeks (January latest), we'll be adding persistence to Hide on this page so you will only have to do this once. We're also exploring syncing this list across all browsers/profiles with that account(s) present so you don't have to repeat this process again and again.

Keep on eye on the release notes to know when this feature will make it into the beta and then the stable version in the future.

That would be nice, if I could say "don't do autofill on https://localhost/my-app/*" and have that stick.

I'll pass along your suggestion to add support for wildcards in the future. Thank you for the feedback! For the time being, have you considered using a dedicated browser profile that doesn't have 1Password installed in it for your development work?

-Dave

ref: PB-44001955

Terms & ConditionsAccessibility statement

©2026 1Password. All rights reserved.
4711 Yonge St, 10th Floor, Toronto Ontario, M2N 6K8, Canada