Hello,
I understand that Firefox aims to be user-friendly. But after all the problems with unwanted autofill of login/password fields in registration forms — and putting… (přečíst více)
Hello,
I understand that Firefox aims to be user-friendly. But after all the problems with unwanted autofill of login/password fields in registration forms — and putting aside the security issue of prefilled passwords being easily revealed...
…I’ve run into what looks like a bug in the autofill logic.
In my form, I have:
a billing contact section, with an input name="data[inv][email]"
and a login section, with name="signLogin" and name="signPwd"
Now tell me — what do you think the user expects to see prefilled when logging in?
The billing email? Or maybe the actual login input?
Right now, Firefox decides that the billing field is a better candidate for autofill.
Which makes me wonder… is your detection logic just matching the first input with a name that fits /^email$/?
Because if that’s the case — seriously — maybe someone working on the heuristics should pause and think.
Blasting credentials into random inputs just because the name looks vaguely like "email" is not a smart strategy.
This isn’t meant to insult anyone.
It’s a bug report. And a bit of constructive sarcasm, yes — because this has a real impact on UX and user trust.
Attached screenshot is from my dev environment.
It shows the autofill behavior clearly:
The password field is autofilled.
The actual login field remains empty.
Instead, the billing contact email field (with name data[inv][email]) gets filled
This is not expected behavior, and highlights the flaw in autofill heuristics.
Best regards,
Pavel
PS: Translated from my native language into English using a translator.
