tpetrov
(Toni Petrov)
Novembre 13, 2020, 4:08
1
Je voulais Ă©crire Ă ce sujet, mais jâai vu que cela avait dĂ©jĂ Ă©tĂ© soulevĂ© :
I agree that itâs not necessary by default because itâs a short form, but itâs bad that we do two different things when custom fields are present. We do already have a class in there when custom fields are present, so I think itâs an easy change to show asterisks for all required fields in that case.
En bref, lorsque vous avez des champs personnalisĂ©s obligatoires, ils sâaffichent avec un astĂ©risque, mais les champs principaux, par exemple lâe-mail, le nom dâutilisateur, etc., nâen ont pas, alors quâils sont Ă©galement obligatoires, ce qui est un peu confus.
5 « J'aime »
I have a pull request for this ready for review here:
master â awesomerobot:required-fields
merged 11:26PM - 07 Dec 20 UTC
When custom user fields are required at signup we show an asterisk to label them⊠as required... but we don't do this for our default inputs. For the sake of consistency, this change adds an asterisk to our default sign-up fields only if custom user fields are present.
This is a compromise between being simple by default, and consistent with added customization.


Relevant discussion here: https://meta.discourse.org/t/required-should-be-next-to-all-required-fields-in-sign-up-form/126235 and more recently here: https://meta.discourse.org/t/required-fields-not-shown-as-required-during-sign-up/170052
This may not be merged for a week or two because weâre preparing for our next major release and changes that arenât immediately necessary are on hold.
Iâll update when this topic when itâs been merged.
5 « J'aime »
The above change has been merged in, so youâll see the fields marked as required the next time your site is updated.
4 « J'aime »
awesomerobot
(Kris)
A scindé ce sujet ()
Novembre 12, 2024, 2:36
4