Latest Chrome Addon 3.8.10 will fill incorrect data

I have login data for a vBulletin3 forum saved in KeePass
Both Chrome and Firefox Addons used to work fine in the past

Starting with the last Chrome Addon update (3.8.10), the Kee addon will now always put the string “User Name” in the username field and some 8 char long string (presumably “Password”) in the password field.

I can still click on the icon next to the fields an choose the one available entry to fill out the correct login information, but automatic fill when opening the page in Chrome will always put “User Name” in the field.

The Firefox plugin (3.7.8) still works correctly.

Other pages (besides the mentioned vBulletin forum) will also work fine with the Chrome Addon

Still the same problem with the Chrome plugin version 3.9.

The Firefox plugin meanwhile has been updated to 3.8 and now fails with the same problem.

The detailed list of changes between 3.7 and 3.8 is at Comparing 3.7.8...3.8.10 · kee-org/browser-addon · GitHub

I don’t see how any of them could change the behaviour on a specific page in the way you’ve described except for the one that adds the new “Automatically fill fields that already contain text” preference as mentioned in the release notes. Did you try changing that setting to see if this is the change that alters the behaviour of that form? Perhaps you have other extensions that can change the contents of the form or maybe the web page changed something coincidentally (sometimes web site changes can roll out to different browsers at different speeds).

Enabling that setting worked, thank you. I had read about it, but it didn’t seem to fit, because the password field has no default value, but there was still some 8 character string put into it.

Login code below:

  <td class="smallfont" style="white-space: nowrap;"><label for="navbar_username">User Name</label></td>
  <td><input type="text" class="bginput" style="font-size: 11px" name="vb_login_username" id="navbar_username" size="10" accesskey="u" tabindex="101" value="User Name" onfocus="if (this.value == 'User Name') this.value = '';" /></td>
  <td class="smallfont" nowrap="nowrap"><label for="cb_cookieuser_navbar"><input type="checkbox" name="cookieuser" value="1" tabindex="103" id="cb_cookieuser_navbar" accesskey="c" />Remember Me?</label></td>
  <td class="smallfont"><label for="navbar_password">Password</label></td>
  <td><input type="password" class="bginput" style="font-size: 11px" name="vb_login_password" id="navbar_password" size="10" tabindex="102" /></td>
  <td><input type="submit" class="button" value="Log in" tabindex="104" title="Enter your username and password in the boxes provided to login, or click the 'register' button to create a profile for yourself." accesskey="s" /></td>

Yeah the problem is that they force the actual value of the form fields to be “User Name” etc. and then use Javascript to clear that value when you click on it. This is something that websites had to do around 15 years ago before the “placeholder” feature was added to web browsers.

There are thankfully very few websites that still use that old approach because it’s poor for accessibility but this is a great example of why I wanted to make that new feature optional. I wasn’t sure if any actively used websites would still have such old code but expected some rare exceptions so it’s useful to get the feedback from you that this is the case.

I think that if you keep the option disabled, you should still be able to ask Kee to manually fill your credentials to the form so it’s up to you if that’s a better compromise compared to the risk of having important "value"s in form fields being accidentally overwritten by Kee - I think it’s best to just spend some time with the option enabled and see how you get on.