v16/v17 should add data attributes for major password managers to not interfere with the DOM

[Jeavon]

Which Umbraco version are you using?

16.3.4

Bug summary

Following on from forum discussion - https://forum.umbraco.com/t/browserextensions-making-the-backoffice-slow/6214/15

Password managers attempt to autofill all form fields, this can make working with Umbraco very slow or unusable, the major password manager vendors support different data attributes to tell them not to autofill.

Example markup for major password manager vendors

<div id="tiptap-editor"
     contenteditable="true"
     data-form-type="other"       <!-- Dashlane -->
     data-lpignore="true"         <!-- LastPass -->
     data-1p-ignore               <!-- 1Password -->
     data-bwignore>               <!-- Bitwarden -->
  <!-- TipTap editor content goes here -->
</div>

Specifics

No response

Steps to reproduce

Install Dashlane and try to use the Umbraco v16/v17 backoffice with a few RTE editors loaded

Expected result / actual result

No response

[github-actions]

Hi there @Jeavon!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[umbracocommunity]

This issue has been mentioned on Umbraco community forum. There might be relevant details there:

https://forum.umbraco.com/t/browserextensions-making-the-backoffice-slow/6214/20

[nielslyngsoe]

Fantastic, it's a good idea to do this!

I have not investigated if this could work or would be problematic — but an idea: Would it make sense to apply these attributes on a higher level? Like for the whole workspace? On all Workspaces, except the member and user?

[Jeavon]

I have not investigated if this could work or would be problematic — but an idea: Would it make sense to apply these attributes on a higher level? Like for the whole workspace? On all Workspaces, except the member and user?

I would say everything except for the login, what reason is there that you'd need a password manager to autofill anything within Umbraco except for the login screen

[madsrasmussen]

A couple of notes from yesterday’s testing related to the opened PR #20905

• The Dashlane browser extension will, on its own, bring down the Backoffice performance significantly. We have tested with Dashlane as the only activated browser extension. See the video for an example. First, without Dashlane activated, and afterwards with Dashlane activated.
• The password manager attributes need to be added directly to a native input field to take action. This means that the implementation has to be made in the UI Library. Each affected input could implement an ignore-password-managers attribute that would apply the correct attributes to the native input field in the implementation.
• From what we can see, the password manager attributes won’t prevent the browser extensions from analyzing the DOM, which could be what is bringing down the performance. They just prevent the autofill UI from showing up for those specific inputs. The Dashlane extension will still assign a Dashlane ID to each input.
• We haven’t found a solution to disable the password manager for an entire “area” where we can prevent them from analyzing the DOM.

Screen.Recording.2025-11-28.at.09.38.50.mov