Disabling 1Password X for specific fields/forms (web developer question)

pbhoganpbhogan Junior Member

Hi—I'm a web developer and an avid 1Password user. I've found that 1Password X and its icon is showing in every field of some forms quite aggressively. I presume it tries to only do so on fields where it thinks it's in a login form, but it's showing in places it shouldn't. It ends up interfering with things like typeahead inputs and anything with custom keyboard press handlers and just generally gets in the way where it shouldn't.

Could you shed some light on how it's choosing to where to show up, and perhaps more importantly for developers like me, is there a specific per-form or per-input attribute we can use to disable it?

As a concrete example, I'm working on an enterprise web application that has a form for editing accounts, so the word "account" is part of the form id and there are username fields and whatnot. This is probably what is triggering 1Password X to insert itself. Unfortunately, 1Password is not actually useful in this context of managing the several thousand accounts of other people in this application and makes a nuisance of itself. :)

Besides having per-form and per-input blacklist attributes, it would be super useful to be able to mark any html with an attribute (e.g. to disable 1Password on child elements and only whitelist specific input fields with a similar attribute (e.g. ) to indicate where it's safe to use. This would give tighter control to app developers who are dealing with issues like this without affecting normal operation of the plugin.

Keep up the great work!

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided


  • pbhoganpbhogan Junior Member

    Hah, I should have known better than to put html in a form. My examples were (excluding the angle brackets):
    body allow-1password="no"
    input name="username" allow-1password="yes"

  • dtearedteare Agile Founder

    Team Member

    This is a great question, @pbhogan. You're right, 1Password is analyzing the page looking for interesting things. Login, registration, and credit card forms are things we're very interested in and decorate them. While things like search fields we want to avoid like the plague.

    Most likely it's exactly as you say: you have the word account in your form and 1Password thinks it's a registration form and jumps in to help. But given that we used machine learning to create the form analyzer, it's not immediately apparent that this is the case. 🙂

    At this moment there is no mechanism to control form categorization like you described. This is something we will likely add in a future update as developers like yourself should be given the tools you need. Pinging @mitch as this is a topic near and dear to his heart.

    Thanks for bringing this up!


  • I came here with the same question / concern.

    Have you considered giving the user an option in the UI to "not suggest for fields like this"....or the opposite, maybe right-click and tell 1Password to suggest? That would give you additional data points for your ML algorithm, and, depending on how your algorithm works, it could allow us developers canto pre-train the system on our UIs before releasing them into to the masses of 1Password users!

  • brentybrenty

    Team Member

    It's a cool idea. Perhaps we'll be able to do something like that down the road. Thanks for the suggestion! :)

  • Same here. I'm tired of having to lock 1Password X everytime I input the user search form in HacknPlan.com.

  • BenBen AWS Team

    Team Member

    Sorry for the inconvenience @LagPick. Thanks for sharing your experience with us. Hopefully this is something we can address.


  • Hello guys,

    I have the same problem.

    I'm a web UI developer, and 1Password User, and 1Password places its icon in fields I'd really rather not have icons in.

    1Password get's particularly exited by a field label/id containing 'mobile number'.

    As my webapp uses the label often, I get the icon scattered randomly throughout my application.

    This looks darn ugly, and is very irritating from a UX perspective.

    I'm sure I could personally disable these icons for my browser, but 1Password is popular, and my concern is for the UX of my user base.

    Is there no standard HTML5 attribute that I can add to my inputs to tell ALL password managers to relax and stop offering to help.

    If not, maybe some 1Password specific tag that will do the trick.

    Any assistance will be most welcome.



  • brentybrenty

    Team Member
    edited November 2019

    @mee: If you'd like to provide more details so we can actually take a look at it and see if there's something we can do to help with your specific case, please email us at [email protected] so we can take a look. :)

  • Hello,
    For example, I'm using Asana, and in the input for Assing task, is always 1password suggesting an password. How could avoid it?

    You can see it here:

  • kaitlynkaitlyn

    Team Member

    Thanks for the report, @davidperezgar! We fixed this issue fairly recently, but it seems to have made its way back. I've passed the report along to our developers so they can take a closer look. In the meantime, you're welcome to try the 1Password X beta, where we'd added the ability to hide the inline menu on a specific page. If you're needing to assign a bunch of tasks at once, that would come in handy. Let me know which browser you use if you're interested in the beta, and I'll send you over the download link.

    ref: dev/core/core#481

  • zindlerbzindlerb
    edited February 4

    One workaround I have found is to replace your input tags with textarea tags. The 1password extension seems to ignore textarea tags. Not a great workaround but if your application is more of an application than a website like asana it might be a good solution.

    In the long run hopefully 1password will publish a class that can be applied to elements to explicitly opt out of their input helper.

  • BenBen AWS Team

    Team Member

    I think one concern with that approach is that there are (perhaps surprisingly) still organizations out there that are anti-password manager. I would be afraid some might use such a feature to try and prevent their users from using password managers at all, rather than trying to create better UX.

    An open letter to banks

    That isn't to say we won't do it, but there are some considerations.


  • edited May 3

    Hi, I hope this doesn't help the banks too much and doesn't hurt people with disabilities, but I was able to work around the issue by setting my label like this: "Invite project members by name or e[special character here]mail" using an invisible comma special character:

    It would be better for 1Password to support an attribute to opt out. They can then choose to ignore it for specific banks.

  • kaitlynkaitlyn

    Team Member

    Thanks for your input on this, @anthonysapien!

  • This is certainly very frustrating as a developer... but perhaps I'm just missing something obvious here? I've made a popup that asks an admin user of my app to enter the email address of a new user that they'd like to add... clearly this would not be in the admin user's 1Password account, but despite me turning autocomplete OFF for this form, 1Password is still popping up for this field.

    Is there an official way to stop it?

    Here's a screenshot:

    Thank you!

  • ag_yaronag_yaron

    Team Member

    Hey @jgrinsted

    We're working on a feature right now that will respect autocomplete=off when there's no password field present. It should be released in the next beta update or so, and it should address the issue you're showing here. Hopefully it will be released soon :)

  • This is an issue for me as well in Robohead. When I try to add reviewers the 1password sign-in blocks the dropdown list so I can't see who I'm choosing and rolling over it will cause the drop down to collapse. See link below for screenshot (the textbox in this comment form is on top of the insert image menu so you can't choose an image just FYI)


  • ag_michaelcag_michaelc

    Team Member

    Hey @SomethingBlue42. If you right-click in that field and choose the "Inspect" option, does that field make use of autocomplete="off"?

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file