Just putting this in here for now so there is a record of it somewhere (I have talked about this on Discord previously). But I use the password manager 1Password as I know a lot of others do. It works in pretty much every other website, but for some reason on the Latenode login page it always prompts me to create a new password in the password field.
Not a biggie but it’s annoying because I then have to go into 1Password and copy the password then paste it in.
I’ve messaged the 1Password support team who have verified the issue is happening on their side as well, but the HTML structure looks as they’d expect. They’re going to do some more testing and see why it’s happening. I’ll update everyone when I know more.
Update from 1Password so far:
"I looked through everything and matched it with our developers documents and I can’t see anything on my end that can indicate an issue. There may be a slight difference, but I’m not seeing it completely. However, it does look like 1Password is recognizing the fields as an Identity field instead of a login item. I let our developers know and mentioned that you’re close with the website developers so they’ll try to help in the best way possible.
One of our developers sent over some feedback about the website, why it’s happening, and a possible workaround. This seems to be happening from our end mostly and it’s because 1Password thinks the fields are identity fields instead of login fields, which our developers will look into.
As for a workaround, the “forms:” section is currently:
{
"headerText": "Sign in Start automating your processes today",
"htmlAction": "https://app.latenode.com/auth",
"opid": 0,
"textContent": "E-mail * Password * By clicking this button you accept the privacy policy, terms of service Login Don't have an account yet? Create Forgot your password?"
}
If you change it to:
{
"htmlId": "login",
"htmlName": "login",
"headerText": "Sign in Start automating your processes today",
"htmlAction": "https://app.latenode.com/auth",
"opid": 0,
"textContent": "E-mail * Password * By clicking this button you accept the privacy policy, terms of service Login Don't have an account yet? Create Forgot your password?"
}
1Password will recognize the fields as a login field instead of a sign up field by adding “hmtlId” : “login” and htmlName “login”. If you’d like to forward this to the websites team and if they have any questions, let me know.
I asked them about this and this is what they said:
I understand that the code has not changed yet. Please let us know how it goes and we will update our internal issue accordingly.
Regarding what you mentioned:
“But it seems that if you click the autofill button in the chrome extension then it does recognise the password field… But if you click the field it doesn’t (which is my normal workflow).”
This is expected and it is actually a workaround I’d recommend for situations like this. The root cause of the issue is that 1Password detects the form as a sign-up form rather than a login form, but it won’t affect the autofill function of the login item. Once the form structure is modified, 1Password should suggest login items properly.
I’m looking forward to your updates.
@Oleg@Raian how simple would it be to modify the HTML on the login page as they suggest?
Legend! Thanks heaps could you update me once you decide something so I can update 1Password. Or I could just link them up to your help@ email in the same chain.
