henriet

Hey Caleb ??
Thanks for passing it on, at least the devs can check it then.

Firefox (and obviously Chrome, because threesixnine encountered it there as well) can save your username/pass, and that’s what it’s doing for me. So that part is fine.
It just shouldn’t be filled into the wrong field with these woocommerce-settings, and indeed it didn’t do that before the update.
Hope the devs can figure out where the problem is!

Thanks for your time on this issue :).

Hey Caleb, thanks again! ??

It’s fine that Firefox fills out the form, the problem is that it’s using the wrong field for it now. It started happening after upgrading to WordPress 4.6, it didn’t use the wrong field before. In 4.5.3 the browser still recognises that the field is not there and simply ignores the username because of that (which is correct behaviour!).

Unfortunately, this problem is not something I can solve by a change in my settings or in my website (and yes, I’ve searched for that and now again as you suggested so). -> https://support.mozilla.org/en-US/kb/control-whether-firefox-automatically-fills-forms

It looks like the browser is no longer being “told” (by Woocomemrce?) that the field for username is not being displayed when you choose these woocommerce-account-options. Maybe something is overriding that or preventing that from happening now.

Perhaps this is something that should be passed on to the devs as right now there appears to be a coding-miscommunication between browser and software? ??

~Henri?t

A bit superfluous perhaps: Screenshot of the create account fields when the customer IS allowed to choose his own username; fields show up as should and there are no problems:
https://prntscr.com/c9962u

Hi Caleb, thanks for your response!

No, that’s not the problem.

It’s about the username and password fields under the “create-an-account” button.
These fields show also at the top for returning customers, but here it works correctly as both fields are always displayed: so username can go to the username field, password (dotted out) to the password field.

This problem however is about the fields below the create-an-account button/checkbox, at the bottom of the shipping fields. When you tick the checkbox, the fields are displayed.

But: if you have turned the account-settings to “generate username from email”, the field for username will not be displayed. Which in itself is logical.

As there is no username field, it is still tried to to autofill in the form. It puts the dotted-oud password in the correct field. There is no room for the username though – but it insists on displaying it anyway and thus chooses the next-best option, which is the first field above the password field.
In my case, this now happens to be the field for city-name, as that’s the last in my field-order. (country is fixed and cannot be edited)

Screenshots:
the fields for returning customer login:
https://prntscr.com/c98jel
the fields around the “create an account”-checkbox:
https://prntscr.com/c98hsx

And yes, my browser (Mozilla Firefox 48.0 and now 48.0.1), do remember my form history, but this is not a dropdown of choices that show up when I start typing. The username and password are already completely filled in when I open these forms.
Perhaps it is Mozilla doing this, and Chrome too as I read above, but certainly they shouldn’t be directed to the wrong field though? That’s why I thought the source of this problem is in Woocommerce (or perhaps even WordPress, as this started happening after upgrading to WP 4.6. Either way there appears to be a new conflict).

Hope I’ve made it a bit clearer now ??

Working with Mozilla Firefox myself (48.0 – and it still does it in 48.0.1, just upgraded).

Glad I’m not the only one to encounter this!
Yup that’s a way I could try and tackle it too, but that would only be at my end and not at that of the customer. I rather see things from their end too, so I know if everything’s fine or not. It looks a bit unprofessional now ??
If a browser autofills a field in the wrong place/wrong way, then evidently something is amiss in the coding, in my opinion. Really hope that it’s picked up and dealt with ??

Reordered my fields, making my username now end up in the city name…