# Conflicts with Discourse and 1Password 7 Beta in Safari

**URL:** https://meta.discourse.org/t/conflicts-with-discourse-and-1password-7-beta-in-safari/160066
**Category:** Feature
**Created:** [August 6, 2020, 6:34pm UTC](https://meta.discourse.org/t/conflicts-with-discourse-and-1password-7-beta-in-safari/160066 "2020-08-06T18:34:41Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [August 7, 2020, 5:51pm UTC](https://meta.discourse.org/t/conflicts-with-discourse-and-1password-7-beta-in-safari/160066/5 "2020-08-07T17:51:39Z")

</div>

It looks like 1Password uses machine learning to determine where to activate, so until recently (last month) there was no surefire way to disable it.

[The related support discussion](https://discussions.agilebits.com/discussion/96661/disabling-1password-x-for-specific-fields-forms-web-developer-question) says they recently started checking for `autocomplete=off`… but we’re already using `autocomplete=discourse` [because Chrome ignores `autocomplete=off`](https://meta.discourse.org/t/new-post-reply-sometimes-tries-to-autocomplete-my-address-on-chrome/107484/66) and tries to autocomplete with their saved form data 🙃

---

_[View the full topic](https://meta.discourse.org/t/conflicts-with-discourse-and-1password-7-beta-in-safari/160066)._