Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Feature request: Hide 1Password on an entire website
I'm trying to figure out how to disable 1Password for specific websites. I understand that the first time I visit a url have the option to "Never Ask Again," but I don't know how to manually enable t...
Hello folks!
As mentioned by Evon a year ago here, 1Password can now be permanently hidden on specific URLs in your browser by following these steps:
- Right-click on the page in question.
- Choose 1Password - Password Manager > Hide on this page.
This will hide 1Password on that specific page (URL) but not the entire website. This preference will persist even if you close or restart your browser. To clear your hidden pages you can right-click on the 1Password icon in your browser's toolbar, click Autofill & save, and then click Reset hidden pages.That said, the internal feature request to expand this feature so you can hide 1Password across an entire website (not just a single page) is still open with the product team. Please keep the feedback coming, it really helps us understand how we can continue improving 1Password to better fit your needs.
-Dave
Hi, I'm joining the queue in this thread to complain about the autofill malfunction.
This is an issue that 1Password has been carrying for a long time, and I believe it's time to provide a response to the customers who pay for their subscriptions meticulously but for whom there is still no solution.
In reality, the problem to solve is quite simple. I understand that you want to use the domain name for filtering, but I think you should give users the option to choose the type of filtering:
domain name
or
text string or url "call it whatever you want, in the end, it's just a simple string of text"
The autofill, if it finds the autofill set to a text string or url value, will perform a simple comparison.
Does the page contain this URL? If yes, it does not perform autofill; otherwise, it does.
Delaying the solution to this poorly designed feature, I don’t think, can even be attributed to the number of URL variables that a user inputs because, let’s be honest, I don’t believe the average user has more than 30 or 50 items with custom URLs. Normally, when an item is saved, the first URL entered is then used. This applies to 99% of the items saved in the vault.
Providing the ability to execute a filter based on a string/URL more complex than just the domain name is an important feature.
It's been years since the first complaints about this issue. When do you plan to solve it?
