IYA.APP is a Chinese forum site powered by Discuz! version X3.4. (The site does not support registering recently, but the issue can be reproduced without an account.)
I can’t reproduce this problem with the Kee 3.0 beta on Firefox 66. Either it’s something I’ve fixed in that version or some other software is causing a compatibility problem. Please can you check with Kee 3.0 and let us know if that fixes the problem?
Hi, thank you for your reply. I just installed Kee 3.0 kee-3.0.1beta-an+fx.xpi on my Firefox 55.0.2 which is the latest release on my Windows and the problem was reproduced.
I’ve found out that the site uses the following code:
// excerpt from https://iya.app/data/cache/logging.js?hF1
// in the HTML, the "login" button has onclick=lsSubmit();
function lsSubmit(op) {
// unrelated part skipped
if ($('ls_username').value == '' || $('ls_password').value == '') {
showWindow('login', 'member.php?mod=logging&action=login' + (op ? '&cookietime=1' : ''));
} else {
ajaxpost('lsform', 'return_ls', 'return_ls');
}
return false;
}
If Kee is loaded before the login button is clicked, $('ls_username').value and $('ls_password').value would be set to the corresponding item in my KeePass database, so the program would go to the else branch, but the CAPTCHA forms are not filled yet, so the ajax login would fail.
One possible solution may be disabling auto-fill on page load on this site, then I can click the Kee button to fill the form after the login window displays, but there is no configuration on this yet.
Ah OK, so it’s not that enabling Kee causes the problem. In fact, it is that any auto-fill operation on their login form will trigger this bug in their website.
Without studying their site in detail I can’t say for sure but it looks like the correct fix would be for them to change their code so that it also checks for the CAPTCHA form completion status (presumably the captcha has been added later without regard to this code sample you provided).
In any case, doesn’t disabling auto-fill for the entry in question work around the issue?
You’re correct that you can’t disable auto-fill on a per-site basis but that should only be helpful if you have a huge number of entries for a site.
If you’re happy with the solution that’s great, although it sounds as though you’ve blacklisted the entire form which would prevent you from even manually invoking Kee to fill the login form when it has been displayed. I was referring to the option in each KeePass entry that controls auto-fill behaviour for that entry (i.e. go to KeePass, Edit the entry, go to the Kee tab and change the settings there).
Glad you’re looking forward to Kee 3.0 on Chrome. I’m waiting for at least another week to give the localisation team time to translate into multiple languages (and for a few other things) so hopefully it won’t be too much longer to wait.
