1Password makes development unnecessarily painful!

Please provide a way to NOT attach 1p to a given (set of) pages.

I really, REALLY NEED to NOT have 1p active on pages served from localhost, for instance.
There are other servers I would like to block 1p from as well, of course (consider how s/w goes through dev/test/xcpt/prod cycles)...but localhost is the most important/frequently aggravating example.

I have seen:
https://1password.community/discussion/133575/hide-on-this-page-does-not-work

Agree wholeheartedly that this is a BIG pain-point.

Please (re)examine this with a bit more importance.


1Password Version: 8.10.5
Extension Version: 2.10.0
OS Version: win 11
Browser:_ edge (also chrome, firefox)

Comments

  • Hey @1pBob,

    I'm sorry for the delay in getting back to you.

    Thank you for your feedback, I can totally understand where you are coming from and I have put in a request with our product team along with all of your comments to see if we can make improvements in a future update.

    Thank you for taking the time to suggest ways in which we can improve 1Password and I'm sorry for any inconvenience caused.

    ref: PB32874665

This discussion has been closed.