Some websites don't detect the fields as filled in

[funkydude]

I'm starting to notice a growing issue with some websites. When the username/password is filled in automatically and you attempt to click submit, the website will not allow you as it thinks the fields are empty.

The latest website I noticed this on was dominos.co.uk I'll add more as I encounter them as I cannot recall them off the top of my head.

Using Chrome.

[mrrsm]

I noticed this as well. I think it is expecting an event (keyup, change, etc) that isn't being fired when autofilling the fields.

[funkydude]

IndieGoGo is another one. In this case, you must click the login button which opens a popup (which isn't automatically filled in). When you right-click the input field and select fill user+pass, then click login, it will fail. Manually pasting the input into the fields works.

[Draugor]

i have the same issue with g2a.com (or the be specific with https://id.g2a.com/login) using Chromepass 2.6.8 and KeePassHttp 1.8.4.0

[funkydude]

Spotify.com is yet another one, when attempting to sign in. @pfn have you abandoned this project?

[pfn]

I am looking for volunteers to pick up more maintenance of it. It is extremely low on my priority list as it generally works well enough for me and I have other fish that need frying. (There are PRs I haven't had time to get to either :-/)

On Mon, Feb 22, 2016 at 4:28 PM funkydude notifications@github.com wrote:

Spotify.com is yet another one, when attempting to sign in. @pfn https://github.com/pfn have you abandoned this project?

— Reply to this email directly or view it on GitHub https://github.com/pfn/passifox/issues/463#issuecomment-187451682.

[jtbraun]

This occurs on Instagram.com too.

[marcelser]

Can someone please merge and release a new version of ChromeIPass because this issue is really a pain in the ass. I tried to fix myself but was not successful. If this fix from @jacoB1123 helps then please merge and release

[funkydude]

I hadn't even realized someone had made a fix, @JaCoB1123 should have posted here, but @pfn should definitely look into merging this since the issue itself renders the entire extension useless.

[pfn]

He can make a pr when he feels it is ready

On Tue, Jun 7, 2016, 7:57 AM funkydude notifications@github.com wrote:

I hadn't even realized someone had made a fix, @JaCoB1123 https://github.com/JaCoB1123 should have posted here, but @pfn https://github.com/pfn should definitely look into merging this since the issue itself renders the entire extension useless.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pfn/passifox/issues/463#issuecomment-224307447, or mute the thread https://github.com/notifications/unsubscribe/AAfQxdL0BB0cv1xNWWZw_rUfgWtYLw-gks5qJYbFgaJpZM4HWq5v .

[jtbraun]

I merged and ran @JaCoB1123's notify_of_changes branch, and I can confirm that Instagram.com now accepts the chromipass-filled fields.

[JaCoB1123]

I actually opened a PR (pfn/passifox/pull/513) a week ago. I should have posted here and linked to it probably.

[marcelser]

I also merged the notify_of_changes branch and can cofirm that it also works well on IndieGogo. So it looks very promising. Even if not all pages work. If most work fine it's a fix I've been waiting for months. If you don't want to wait till the stuff is merged. Just checkout jacobs branch and repack the extension in chrome into a crx and import it, that's what I did as this project doesn't seem very active atm. This way you can immediately benefit.

[JaCoB1123]

I tested it on

• fastmail.com
• sparkpost.com
• indiegogo.com

and they all work now. If you find a site where it still doesn't work - let me know.

[marcelser]

Actually using a crx is a pain in the ass as you have to create a special file or Windows registry entry and provide a URL to Chrome, otherwise it disable the crx on next start. So @JaCoB1123 please send a pr to @pfn to update it as he mentioned 1 day ago.

[pfn]

Pr is already there, it was submitted while I was on vacation, I'll review it when I get a chance

On Wed, Jun 8, 2016, 9:58 PM Marc Elser notifications@github.com wrote:

Actually using a crx is a pain in the ass as you have to create a special file or Windows registry entry and provide a URL to Chrome, otherwise it disable the crx on next start. So @JaCoB1123 https://github.com/JaCoB1123 please send a pr to @pfn https://github.com/pfn to update it as he mentioned 1 day ago.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pfn/passifox/issues/463#issuecomment-224800146, or mute the thread https://github.com/notifications/unsubscribe/AAfQxbbtom1gAZCoXW2IoODNeCIZgqwhks5qJ52BgaJpZM4HWq5v .