How to configure the new Contextual Kee buttons

[luckyrat]

The issue below is potentially related. Needs more planning to establish if there should be independent configurability for the contextual button and form filling but we need to at least consider the overlap.

Potential feature: Ignore some fields

Needs more detailed use cases and specification. 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.…