Firefox and Chrome not picking up password field (for auto-filling)

[kasbah]

Tested on Firefox 64.0 and Google Chrome 70.0.3538.102 on Linux.

[renschler]

1Password doesn't detect the fields for auto-filling either. I think it's related to this issue. Tested in Chrome and Brave with 1Password extension.

[swyxio]

no idea whats the cause. open to ideas

[renschler]

I did some research here, what I found said password managers look for a <label for="email"> element above the <input> (ie a sibling element, today I see the input is a child of the label). I also saw that the id of the input should be set to "email".

kenkeiter/skeuocard#42

The same goes for the password field.

However... I tried this out by directly editing the html so that it conformed to the recommendations, and things still didn't work. Maybe because the html needs to be like that when the page first loads? No idea.

In any case, I posted a question on the 1Password forum, will see if anyone responds.

[renschler]

A 1Password team member responded:

I don't know for certain but I suspect the issue is the iframe used for the widget has the source set as src="about:blank" and the extension requires a proper URL. I'm not sure how to easily test that theory though given the point of an iframe is to load an external page.

[Jinksi]

Should we try adding autocomplete attributes?

https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete

[Jinksi]

I've been able to get Chrome to save the password credentials, but not autocomplete on a repeat visit.

Demo: https://wonderful-bell-ea255a.netlify.com/
Branch: master...Jinksi:autocomplete

Probably still a problem with using src="about:blank" as @renschler mentioned

[mnoorenberghe]

The issue is due to about:blank. Password managers save passwords according to the URL/origin of the document containing the login fields (about:blank in this case) but saving/filling for about:blank wouldn't make sense and would introduce security issues.

Based on #17, I think the iframe was used for encapsulation so maybe Shadow DOM is a viable alternative option now?

[mnoorenberghe]

This problem still exists from what I can tell:

netlify-identity-widget/src/netlify-identity.js

Line 269 in 82392ef

iframe.src = "about:blank";

My #275 will only help when this bug is also fixed.

[jlengstorf]

thanks @mnoorenberghe — we'll dig into this

[siamkreative]

FYI, Bitwarden is not able to fill out the credentials. I would assume it's the same behaviors for other password managers.

[kimlai]

Hi all,

I've made a pull request to use Shadow DOM instead of an iframe if anyone wants to take a look.

[renschler]

@kimlai I'm not a github expert but I think you need to add a label to the pull request, and then it'll pass all the checks and maybe someone will be able to review it.

[kimlai]

Hi @renschler, I don't think that's it because I don't can't add labels on pull requests in this repository.

[renschler]

oh @kimlai gotcha.

@jlengstorf could @kimlai's PR be merged in? I get a decent amount of support requests (~1hr / week) related to this.

[scouten]

I've recently run into this issue as well. What can we do to bump this along? New discussion from this last week:

https://1password.community/discussion/comment/602215#Comment_602215

[galencorey]

Any updates here? Running into this issue myself.

[stuible]

Ran into this issue on a client website and would love to see this resolved

[bvdekeer]

Also still seem to have this issue. This is very un-userfriendly especially on mobile.

[mashdot]

A nudge for this, as I believe it should be basic behaviour nowadays (2022). Thanks.

[HeyITGuyFixIt]

@jlengstorf Looks like there has been a fix for this available (#416) going on 2 years. Can you look into this or ask someone to look into this?

[mashdot]

Another nudge to get some eyes on this and #416

[wiredacorn]

Any updates on this?

[mashdot]

@wiredacorn damn you teased with this alert, I thought it was an update 😄