Passbolt’s browser extension does not consistently recognize username fields on several websites used daily by me and my users. In the cases I examined, these sites used unconventional identifiers for their login inputs: non-standard id, name, title, or placeholder attributes. However, these fields still included strings such as “user” or “login” within their attributes.
I propose enhancing the field-detection logic to perform a broader substring check across form attributes. Detecting whether “user” or “login” appears anywhere within those values would increase compatibility with websites that do not follow common naming conventions.
This improvement would significantly reduce the number of sites where Passbolt fails to identify the username field.
I have implemented this modification in a custom build of the extension and confirmed that it resolves the issue. However, maintaining a private build for every new release and distributing it manually to all users is not feasible. Integrating this improvement upstream would ensure consistent behavior for all users.