Turning off field suggestions

Hey @BenjaminHD ,

In your case, there are two possible solutions here:
- You can disable the inline menu's automatic appearance so that 1Password won't show up on its own in fields when you focus them. Simply right-click the 1Password extension icon on the top right corner of your browser, select "Settings", then turn off the "Show autofill menu on field focus". That will apply to all websites, and you will be able to call 1Password whenever you'd like by simply clicking its little icon that shows up on the right side of the field you want to autofill.
- You can send us the details of the page where you don't want 1Password to show up in and we can change that behavior on our side, but that might take a little while to implement. If you'd like to go for it, let me know and I'll provide you with instructions :)

Hi there. I would like to bring the thread back to the autofill experience for users. I hope that's ok.

Our use case is that we use a patient management application across different browser profiles. In that patient management application, we enter demographic data for patients including, among other things, their street address, email address and mobile numbers.

1Password pops up to offer the information we have set up for ourselves in these fields. We don't want to enter our data in those fields! We need to enter the patients' data.

After reading this thread, I have successfully experimented with:

• the escape key option
• the hide on this page feature

But after logging out then back in, it appears that I need to choose either option again to prevent autofill displaying in these fields.

Is there a way to set either of these options or is there another solution so that pages inside the web application never trigger the 1Password pop-up?

Thank you!

I'd like to echo the sentiments made by others before me — on the lightspeedhq.com team I've been stuck choosing between disabling the browser autofill on Chrome or 1pass, but not both.

However, after trying out ag_chantelle's https://1password.community/discussion/comment/606453/#Comment_606453, it works! Albeit as a hacky solution.

To those following along at home: If you include autocomplete="new-password" and id="search-<whatever-you-want>" on your input then browser autofill will be disabled on all major browsers AND 1password.

Here's a simple reduced test case to demonstrate the issue and the fix: https://codepen.io/ls-andrew-borstein/pen/VwWjoEM

Autofill enabled: 🚫 1pass ✅ Chrome

Autofill enabled: ✅ 1pass 🚫 Chrome

Autofill enabled: 🚫 1pass 🚫 Chrome (🎉)

@scotttrinh

You are most welcome! :) If there's anything else you need, do not hesitate to reach back out!

ag_chantelle Great! This was all helpful, and gives us something to go on.

@scotttrinh

You can code the field as autocomplete="off", which will result in the inline menu being closed when the field is focused. Unfortunately, due to rampant misuse across the web, we can't guarantee that the extension will follow the autocomplete attribute 100% of the time.

An HTML id or HTML name starting or ending with search would also be something you could do without changing how the field is displayed and greatly improve the chance that we don't consider it interesting.

Using an HTML input type="search" should be a guarantee that we wouldn't show up, but this does inform browsers that it is a search field and cause them to react differently. For example, many browsers will display an icon in and clear the field if the user hits esc. Here is an example of a search field that will never display the 1Password inline menu: https://fill.dev/form/search

You might also find these links helpful:

• The HTML spec standard for autofilling: https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofill
• Our basic guide for developers: https://support.1password.com/compatible-website-design/
• Additional sample forms we use to test filling (login, signup, credit card etc): https://fill.dev/

I hope this information will point you in the right direction.

@ag_ana @ag_yaron

Apologies for hijacking this thread, but is there something that we as web application developers can do about this issue from the other side? We have multiple fields that end up getting these inline suggestions and they get reported as bugs to us, but I can't seem to find best practices or suggestions on how to avoid 1password filling a field.

You are welcome @mskopel! I am glad we could help :)

If you have any other questions, please feel free to reach out anytime.

Have a wonderful day :)

Thanks to you both. The problem was that I was looking for that option in Settings and by clicking on the 1Password extension at the top of the broswer. I have not had cause to click on Suggestions at the field level. All's good and thanks again.

In addition to ag_ana's great suggestion, which will temporarily hide 1Password on this website, if 1Password is showing up in a place where it is not supposed to, please let us know exactly where so we can improve it on our side and prevent it from showing up there :)