REMINDER: the community is in read-only mode until July 2nd. This is part of our platform upgrade! Learn more in the FAQs →
Forum Discussion
New Chrome extension is too offensive, I'd really welcome a bit more customization
Dear Team,
1Password seems to be a very promising, good solution to handle passwords.
Based on my experience it works very well with that part.
However there are still room for improvement w...
ag_chantelle
1Password Team
1Password Team@peterhorvath
The battle to keep 1Password filling properly across every site on the web is a one without a clear endpoint, so we're always appreciative when you take the time to share your experiences. Contact forms do present a unique challenge, since there is no set standard for developers when they create these. So we do our best to fill based on the HTML attributes that web developers use. Although, as you've found, it's far from perfect.
You're not wrong in your statement that Chrome handles this better. The nice thing about Chrome is that it uses autofill and autocomplete history for forms, which makes it easier to fill if you return to the site again.
With that said, it is entirely possible for both Chrome autofill and the new version of 1Password to co-exist. If you wish to use 1Password for filling ONLY Logins, and not contact forms (via Identities), or payment info (via Credit Card items) - you can adjust permissions as outlined in the second topic link you posted. For reference, I'll include them again for you below. Keep in mind, you will need to re-install the new version of 1Password for your browser to implement these settings:
- Right-click 1Password's icon in Chrome's toolbar and click Settings.
- Under "General" turn off the "make 1Password the default password manager" option.
- Paste the following into Chrome's address bar:
chrome://settings/autofill - Click Payment Methods/Addresses and more and and allow Chrome to autofill.
Let me know how that works for you.
