Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chromeIPass fails to detect all entry fields on https://gbg.onlinedisclosures.co.uk/ #345

Closed
cmt29 opened this issue Jan 12, 2015 · 2 comments · Fixed by #349
Closed

chromeIPass fails to detect all entry fields on https://gbg.onlinedisclosures.co.uk/ #345

cmt29 opened this issue Jan 12, 2015 · 2 comments · Fixed by #349

Comments

@cmt29
Copy link

cmt29 commented Jan 12, 2015

I can't seem to get chromeIPass to detect the first entry field on the login at this website: https://gbg.onlinedisclosures.co.uk/. I've programmed a custom field in KeePass2 giving it the required "KPH: " prefix, and modified the keepasshttp settings to allow the use of custom fields. But I can't seem to select the first PIN field when choosing own credentials for the page, nor is it detected automatically. What might I be doing wrong?

Thanks.

@chrahunt
Copy link
Contributor

You aren't doing anything wrong. The field type 'number' isn't one that chromeIPass recognizes. I've made a fix and will submit a pull request to solve this.

@cmt29
Copy link
Author

cmt29 commented Jan 26, 2015

Thanks very much for your response.

I am also having problems with this site:
http://hazelwood.clubsolution.co.uk/proc_intro.asp

I can never get both fields to be recognised.

@pfn pfn closed this as completed in #349 Feb 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants