Turning off field suggestions

+1 on the idea of data-1password-off="true"

Hey siplhium thanks for reaching out. When we run across instances where 1Password is making suggestions where it's not supposed to, we do try to correct the issue on our end. We're not always aware of where these bugs exist though, so we appreciate when users reach out and let us know about it.

As for when users or developers want to turn off suggestions in fields that 1Password typically do fill, our best recommendation is to indeed use the workarounds mentioned previously. That said, I understand those workarounds are not perfect, and I can pass along your input about this to our dev team. We're always looking to improve 1Password, and we truly appreciate the feedback.

I agree that this is is an annoying problem, and really wish 1Password would do better, and do what it ought to do to stay out of the way. I say this as both a web developer and a user. I don't want to have to add special attributes to cover every password manager, or some other extension that misbehaves. Maybe if you develop for a specific set of users who you know have 1Password, maybe an attribute will help, and I don't see any reason why it shouldn't be offered (I don't understand the fear of developers abusing the attribute). But it's really a band-aid, not a real solution. If a user has a browser extension installed and it interferes with their work or experience, that's between the extension provider/vendor and the user. It shouldn't be the developers' concern, and developers shouldn't have to add or change attributes to cater to any extension's behavior. I don't know what the answer is, except for 1Password to work even harder and do better at staying out of the way when it is neither needed or wanted. My fear -- and this is reinforced by the suggestions I've seen in this thread -- is that higher priority is being given to adding new bells and whistles rather than focusing on improving behavior and really looking hard into where 1Password fails to do what it is supposed to do.

Hey nukmicah! I was able to locate your ticket and have replied from there. Thanks for letting us know about this.

I'm having an issue on the SAP Concur expense reporting website where the autofill popup appears where it shouldn't.

I've sent an email with the collected_page_structure.json to mailto:support+x@1password.com as recommended earlier in this thread, so you guys can write whatever custom code you need to stop showing your menu on this site. Note that the 1Password popup is covering the website's autofill popup, which has the correct entry for me 99% of the time.

But further, might you consider adding an "X" button to your inline menu to reduce the annoyance of this for future problematic websites? @ag_yaron suggested three options, (1) Pressing ESC on your keyboard, (2) Clicking on a blank area in the page to remove focus from the field, and (3) Clicking the little 1Password icon on the right side of the field to toggle it off. But (1) and (3) were not intuitive to me, and (2) causes the SAP Concur autofill menu to disappear, too, which is NOT desired behavior (99% of the time it has the proper autofill entry for me at the very top of its list).

Jack_P_1P Man, this is a really stupid issue that's been here a really long time.
Please change the priority on that.

Add support for data attribute: data-1password-off="true" is the easy, fast hot fix for this.

Hey landsman:

Thanks for your feedback. This is something we're continuing to discuss internally, but don't have anything further to share at this time.

Jack

Please, fix this finally!!!

Thank you for the additional helpful information @snapplez .

The autocomplete="off" attribute will be respected if there's no password field on the page. However, if there's a password field (e.g. type="password"), then 1Password will ignore the autocomplete="off" attribute completely.

We'll keep discussing this internally but our main concern remains that developers will abuse the power to disable us in places they shouldn't.
For now, if 1Password shows up incorrectly in places, we urge users to report the website to us and collect the page's structure and send it over (right-click the extension icon -> help -> collect page structure). That way we can improve 1Password on our side and prevent it from showing up on that page, and possibly other pages that are designed similarly. :)

ag_chantelle thank you for replying - i really do appreciate it (and i'm sure others will be glad for the additional information).

we looked at using autocomplete="off" and autocomplete="nope" (yes, that's a real thing) and it doesn't work consistently. as you mentioned the poor use of autocomplete is an issue and therefore not a reliable way for password managers to detect what they should/shouldn't attach to. also technically autocomplete attribute can be applied to the wrapping form element and it's supposed to turn off autocomplete for everything in the form - not sure how well that works in practice - and it doesn't work with 1password.

there are some techniques that attempt to use the wrong type of text input e.g. type="search" - but this is hacky/clumsy. we can do better.

the most obvious (and valid html) method would be a custom attribute - which is supposed start with data- per html spec - and thus the idea for data-1password-ignore (or data-1password-ignore="true"). an alternative, which probably isn't as elegant as html attribute, would be a class value that would disable 1password on and element.

let me explain why i think this is important. on occasion (more than a few times) 1password (and/or lastpass) trigger on an input element where it just shouldn't. i don't know the specific algorithm for how an input is picked or not (the name attribute probably plays into it) - but it can be wrong and results in a confusing user experience.

bad user interface is not ideal but not usually a deal breaker. however, and maybe more importantly, we've applied enormous effort in an attempt to train everyone that weak/reused/bad passwords need to be avoided at all costs - with the recommendation to please USE, and TRUST a password manager. it is the TRUST and CONFIDENCE in the password manager that is critical - and when 1password, or dashlane, or lastpass, etc - do "weird", "odd", or "unexpected" things IT REDUCES THE CONFIDENCE IN THE TOOL (and yes, unfortunately, i've even been asked more than once to DISABLE/REMOVE password managers because of weird behavior).