Disable autofill on new tab wont work

Hello remonbraamse,

Thanks for the detailed write‑up. What you're seeing is RDM's autofill re‑firing on the user‑edit popup: when the HTML Control's specific Password ID doesn't match, it falls back to filling any
<input type="password"> it finds. The "Disable autofill on new tab" checkbox doesn't cover this case, since it applies to links that open in a separate browser context, not to new tabs or popups within the embedded session.

Here are a few things worth trying, in order:

1. On the Login tab, uncheck Autofill on every page navigation so autofill only runs once at initial login.
2. Go to File → Settings → Entry types → Session → Website and toggle the Autofill mode (V1 vs. the newer engine), as they behave differently around popups.
3. If it still fills, try setting Script type to JavaScript on the Login tab and writing a short script that only fills when the login form's field IDs are present. That bypasses the generic fallback entirely.

Reference: https://docs.devolutions.net/rdm/kb/knowledge-base/entry-settings/website-entry-settings/#login

If the popup is still being filled after (1) and (2), could you confirm whether it's same‑origin as the main page, and whether the password input has autocomplete="new-password" or "current-password"? That tells us which autofill path is touching it.

Thanks in advance, and hope this gets you sorted quickly!

Best regards,

Hi Eduard,

Thank you for your reply.
I tested both 1 and 2 and both make no difference. I will try with the script option. Is there something like a library of knowledbase article to help started with the script?

As for you request, the popup is same-origin as the main page and there is no "autocomplete" in the input field. But when I was looking for this I discoverd I looked at the wrong ID when I wrote the post becouse the ID of the password field in the popup is the same as the ID of the password field on the main page. My appologies for that.

Kind regards,
Rémon Braamse

Hi remonbraamse,

No need to apologize at all, that's actually a really useful clarification! It changes the picture a bit: since both password fields share the same ID, the HTML Control matches exactly as configured and fills the pop-up as well as the login form. So the script route is indeed the right next step, because you'll need to gate the autofill on something other than the field ID, typically the URL or path.

I don't have a one‑stop script library to point you at, but the public reference is here under the Login tab description: https://docs.devolutions.net/rdm/kb/knowledge-base/entry-settings/website-entry-settings/#login

The general pattern that works well for cases like yours is:

1. Have the script check the current page URL or path first, and exit early if it's not the login page.
2. Only when it confirms it's the login page, look up the username, password, and login button by their IDs and fill them.

That way, the script runs its full logic only on the login screen, and the pop-up (which lives on a different path) is left alone.

Best regards,