GioGG

Hi Oliver,

Interestingly enough clearing HTML Control ID's from the entry so that both the username and password fields are blank fixes the issue.

These fields were not manually entered they were automatically generated when adding the site to the vault and worked prior to the update that broke the functionality on Firefox as these issues to not appear on either Edge or Chrome browsers.

Hi,

I'm currently running the latest version of the extension and can confirm the problem persists on entries I've not manually amended the HTML ID on (workaround provided)

The issue remains consistent in that the only sites that seem affected are those running invalid SSL certificates or running just http and not https

As per the screen shot on the affected sites the username tends to fill but the password never does.

Adding the correct HTML ID for both the username and password field has fixed the issue on other sites and I have no reason to believe it won't also fix the above site.

Hi Oliver,

Thanks for the reply I've just tested the workaround on a couple of affected sites and it appears to restore autofill functionality on Firefox without affecting Chrome or Edge.

I appreciate you providing a workaround whilst you work on a permanent solution to the issue.

Hi Oliver

below are the answers to your questions - let me know if there's anything else you require to assist in resolving this issue.

• What version of Firefox are you using? - 156.0 (64-bit)

• Are you using macOS, Windows, or Linux? - Windows 11 25H2 Enterprise

• Is the extension connected directly to RDM, or is it connected through Devolutions Cloud or Devolutions Server? - Devolutions Cloud

I have a similar issue affecting only the Firefox extension and only certain sites.

Clicking the fill icon does nothing on the Firefox extension but the same site works fine on both the Edge and Chrome extensions.

This was working fine up until the latest update.

What I can see is that the affected sites are either not running https or have an invalid certificate that may be causing issues with security settings on Firefox that are not affected on Chrome and Edge. This is problematic as Firefox is my primary browser and we have quite a few sties running self-signed certs where this issue is being triggered.