As a web developer, how can I disable 1Password filling for a specific field?

124»

Comments

  • Hey @comter, @yabdab,

    I'm sorry for the delayed response, I have reached out to the team for advice on this one and will let you know when I have any more information.

  • ag_michaelc
    edited September 2023

    Hi @comter @yabdab et al. I just wanted to let you know I've resolved the issues you reported with the 1pignore attribute. This will be fixed in a future update. I appreciate the handy test site! 🙂

    ref: https://gitlab.1password.io/dev/core/core/-/merge_requests/19267

  • comter
    comter
    Community Member

    @yabdab It looks like v2.16.0 of the 1Password browser plugin has taken care of all the issues that were listed on my test table. Can you confirm that your example is also working correctly now?

    Thanks @ag_michaelc and @steph.giles for dealing with and fixing the issues.

  • yabdab
    yabdab
    Community Member

    @comter looks good on my test form 👍

  • Thanks for confirming @comter, @yabdab.

    Let us know if there's anything else we can help with at all.

  • Aalk
    Aalk
    Community Member

    @steph.giles Can the data-1p-ignore attribute also be supported for textarea elements (not just input elements)?

    In my testing, a textarea element with placeholder text containing "email address" triggers 1P's autofill, regardless of the data-1p-ignore attribute.

  • comter
    comter
    Community Member

    I've updated the test table at https://www.comter.codes/data-1p-ignore/test/ with the request by @Aalk. Are you collecting more than one email address? Otherwise, I'm not sure why you'd use a textarea for an email address field?

  • Aalk
    Aalk
    Community Member

    Thanks for updating the test cases!

    Yes, we're allowing users to enter more than one email address.

  • ag_michaelc
    edited January 30

    Can the data-1p-ignore attribute also be supported for textarea elements (not just input elements)?

    @Aalk I just submitted a merge request to fix this. Thanks for reporting; you'll see it fixed in a future release. 😃

    ref: dev/core/core#27556

  • comter
    comter
    Community Member

    As of 1Password browser plugin v2.21.0 the textarea issue has been fixed and I've updated the test conditions at https://www.comter.codes/data-1p-ignore/test/ to reflect this update. @Aalk can you confirm that textarea with data-1p-ignore is now working as expected?

  • gl0tzk0wski
    gl0tzk0wski
    Community Member


    Why this field is offered as a CC? Howto disable/hide the icon?

    The problem is, my customer wants to use 1PW for login page, but no in any record inside CRM. What i can offer, to switch password manager? Because they dont want to disable "Offer to fill and save passwords" in global settings to hide the icon for several fields.

  • Thank you for writing in @gl0tzk0wski.

    1Password uses several heuristics to identify fields. From the shown HTML, it's possible that "card_expires" is influencing that field to look like a credit card expiration date. If you are the developer for this website, if you add the data-1p-ignore attribute, that should tell 1Password to ignore the field. Here's more information on that:

    I hope that helps.

    -Evon

  • awesomerobot
    awesomerobot
    Community Member

    While I appreciate that there is some solution now, it's a little frustrating that it requires 1password specific attribute, it seems unusual to expect developers to add multiple brand-specific attributes to every input they want to disable autocomplete on.

    Even if you want to ignore autocomplete="off" on the critical username and password inputs, it seems heavy handed to also ignore this on any input called "name" or "address" — these are words that can be used in many contexts that do not apply to individuals!

  • Bigtuna00
    Bigtuna00
    Community Member
    edited September 27

    Agreed. This is not a problem website developers can solve. There needs to be an option in the client to 1) teach the heuristics or 2) add our own filters. There's no way I can go to QuickBooks and say "hey can you add this vendor-specific attribute to all your fields?" Meanwhile 1Password is popping up when entering line items in an invoice. Similarly there's no way I can expect 1Password to instantly fix something, and waiting weeks for a fix while having a completely broken UX during tedious data entry is not viable. I need a way to disable this when it happens.