@php Welcome to the forum!
What website?
Are you using these two password managers together, in the same browser? If so, it is likely that the Google password manager is interfering with the proper function of the Bitwarden password manager.
@php Welcome to the forum!
What website?
Are you using these two password managers together, in the same browser? If so, it is likely that the Google password manager is interfering with the proper function of the Bitwarden password manager.
KFC Hong Kong online ordering website: KFC
Iâm not sure if simultaneously using both password managers is indeed the cause. I just did some testing and obtained a weird result:
I test for three cases: (1) only Edge password manager is ON, (2) only Bitwarden is ON, (3) both are OFF. And I also turned off Edge auto fill function of identity information in all cases.
I have no idea why the website can still get my password in case (3)
This is a type of login form that cannot be autofilled using Bitwardenâs inline autofill menu (nor autofill on page load). The reason is that these autofill methods require manipulation of the HTML code at the time that the webpage has been loaded into the active browser tab. However, the KFC login page does not actually contain a login form when it is first loaded; when the âLoginâ tab is clicked, the website executes script, and that script then injects new HTML code into the webpage, making the login form fields appear.
Browser autofill functions have access to low-level hooks that allow them to react to such events, but this is much more difficult (or even impossible) for a third-party password manager like Bitwarden to do.
If you report the KFC website using the following forms, devs may look into whether there is a way to improve autofill on this type of login form:
I see~, thatâs much more complicated than I thought. Thanks for the explanation.