When logging in using forms with some basic captcha functionality or other fields that change with every login operation, Kee will consider the login entry as different to any others already stored in the database and hence, unless disabled by configuration, will ask the user to save the new password.
Could come up with a blacklist/whitelist system? With pre-populated magic names? (what? “captcha”? etc.)
Also worth thinking about context - e.g. “ignore this field” option?
I believe blacklisting fields in specific contexts would be a nice and useful addition.
My use case: I have a DokuWiki site on which the move plugin is installed. This adds a Rename page menu option, which executes some JavaScript that opens a pop-up window to ask for the new page name.
The problem is that Kee thinks that the input field is a username (it is defined like <input name='id' ...>) and overwrites the field’s contents (which defaults to the current page’s name with path, as shown in the pop-up’s title. Incidentally, that can’t easily be copy/pasted due to a JavaScript event to move the pop-up around).
I suggest to add an option in Kee’s context menu to ignore the entry (temporarily or permanently), and restore the input field’s initial contents.
Kee 3.8 (in beta testing now) will not overwrite fields if they already have some content in them. It’s a bit of an experiment and may be reverted before 3.8 is officially released if I hear that the behaviour is generally undesired so please test it and let me know in a week or two whether it has solved the problem with the DokuWiki move plugin or whether it has introduced new problems that are worse than the ones it solves.
On the page https://ess.partena.be/DALA_514130/public/login.aspx there are 3 input fields of type text. The first one (with id=“ctl00_rightSide_PlaceHolder_TextBox_X8”) has attribute “disabled” set (disabled=“disabled”), and as a matter of fact will not contain the username but an “Enterprise ID”. I managed to have the correct behaviour using the “whitelist” possibility, but don’t you think it could be a good idea to ignore input fields with attribute “disabled” set? They are not editable, so anyway no user should enter any username or passwords in it.
Thanks a lot for Kee by the way, very useful an powerful plugin!
