Here's a new batch of sites with problems about chromekeepass HOT 11 CLOSED

@BlaM Thank you, this is useful information.

It pointed me to the issue. It turns out I do check if a username field is visible:
https://github.com/RoelVB/ChromeKeePass/blob/master/src/classes/PageControl.ts#L39-L41
But I don't check this for password fields. I'll try to find some time this weekend to change this.

It still doesn't make sense to me that the dropdown shows up for you, but I'm almost certain checking the visibility of the password field will fix this.

from chromekeepass.

@BlaM Didn't make it this weekend, but did it today.
I will take some time before the fix is published (the update needs to be validated by Google).

from chromekeepass.

Let's see and wait how it works with those multi-step login forms like the one @f1h0 posted from Yandex.

Those might become a problem and I guess they will be more and more common for bigger sites that use federation with big companies (step 1 recognizes if you are coming from company XY and will then send you to the company log in page to actually sign in with your work-login). But to be honest: Those are clumpsy with other password managers as well.

from chromekeepass.

I often use these sites with a lot of clients I help out with.

from chromekeepass.

Thanks.

Beget.com
It looks like this doesn't work when single clicking credentials. But when I double click or use enter it seems to work. Can you confirm this is the same for you?

Yandex
I don't know how to solve this. You have to press "Log in" twice. Before the first login the password field is there, but hidden. But is looks like after you press "log in" they create a new password field (which of course is then empty)
As a workaround when you get at the empty password field you could right click and choose "Redetect fields" under "ChromeKeePass". Then you should be able to enter the password.

NIC
Seems to work fine for me

eLama
Same method as for Yandex. Right click and choose redetect fields.

I'm thinking about a beter way to redetecting fields, but I'm not sure how I'm going to do that yet.

from chromekeepass.

that's what I noticed.
Beget.com
if you access the site via the home page https://beget.com.
I don't have a login field.

Yandex
here's what I do.

your references tried, they didn't work.

ChromeKeePass application is very good, and useful only there are sites where it works badly.

from chromekeepass.

On https://www.namecheap.com/ when I click somewhere on the page the "ChromeKeePass" layer appears in the top left corner.

from chromekeepass.

@BlaM Could you maybe post a screenshot? I don't have any issues there.

from chromekeepass.

Interesting - and yes, you may be right. This is what happens for me:

BUT: If I do the same in incognito mode, nothing happens - so that might be an compatibility issue with another addon I use. I'll try to figure out which one it is and get back to you. Until then feel free to ignore my previous comment ;)

[Update 2020-08-13]
It doesn't seem to be another extension. The problem still occurs with all other Chrome extensions disabled and it also occurs on other pages. Is there a way to know which DOM node the popup "attached" to? Maybe a debug option that adds a data-attribute to the DOM node could help, just to simplify locating the related element?

from chromekeepass.

@BlaM
Could you try this:

1. When on the site
2. Open the DevTools (F12)
3. Goto the console and execute the command $('input[type="password"]')

What's the result? There should appear only one input.

from chromekeepass.

It returns the correct (single) password input field, but that <input> lies inside a hidden <div>.

Quick sidenote: namecheap does not use jQuery, so "$" is the version built in in Chrome - which will always return one element max. I injected jQuery into the page for this test, though.

jQuery('input[type="password"]') returns one password field, jQuery('input[type="password"]:visible') returns no results.

Other fun observation: I don't even have to click on the page to make the chromeKeePass layer appear. It will also appear if I type anything (valid or invalid, does not matter) into the dev console within the first 2 or 3 seconds after loading the page. If I wait longer, then nothing will happen. This is an extremely strange behaviour and I don't really have an explanation for it.

from chromekeepass.