# 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:** 1

<div class="post-metadata">

**Author:** ![galligan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/galligan/32/224839_2.png) [@galligan](https://meta.discourse.org/u/galligan)\
**Post date:** [August 6, 2020, 6:34pm UTC](https://meta.discourse.org/t/conflicts-with-discourse-and-1password-7-beta-in-safari/160066/1 "2020-08-06T18:34:42Z")

</div>

Currently running [1Password 7.7 Beta-2](https://support.1password.com/betas/) in Safari, which now has the 1PasswordX-like auto-fill feature of certain fields. Right now it’s treating any field that might contain usernames as an autocomplete field for 1Password to fill. That in turns is overriding the Discourse options, rendering type-and-search useless. See image:

 ![CleanShot 2020-08-06 at 14.26.35@2x](https://global.discourse-cdn.com/meta/original/3X/9/e/9e30e2347db4af85f318fb072424db5c105a66ae.png)

I did some digging on 1Password’s website to see how to potentially disable this in the HTML and found this:

> **[Design your website to work best with 1Password - 1Password Developer](https://www.1password.dev/web/compatible-website-design)**
>
> Learn how to make sure 1Password correctly fills forms and generates passwords on your website by following these design guidelines.

---

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