Turning off field suggestions

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.