The discussion revolves around improving the UX on signup when a user has not completed all required fields. sam points out that the current error message is not helpful and suggests two improvements: scrolling to the unfilled field and making the error message more specific. They also suggest removing the disabled button and instead popping an error that teaches users why they cannot create an account.
codinghorror notes that having many required fields can be a problem, but agrees that making the error message more literal can be a good fix. sam responds that four required fields is not excessive.
sam requests that the error message be updated to specify the exact field that is missing, and nathank agrees that this would have helped in their previous experience with signing up multiple users. vinothkannans confirms that the correct error message has been added and merged in PR #9643.
Guess what I did not fill?
That’s right … good guess:
Instead:
We should at least scroll it so the field that is not filled in is on the screen
We should possibly make error message more specific: "You have not completed the Sector field".
Also:
We should stop doing this:
Button should not be disabled ever, just pop an error that teaches users why they can not create an account.
I mean, maybe – but if you have that many required fields you are shooting yourself in the foot so hard that the floor underneath you may collapse at any time.
Easiest fix for the moment is to be literal in the error about which field of the 62 required was not filled out.
4 required fields is A LOT, but not a super catastrophe imo, the fold when signing in via GitHub is just in a super unfortunate spot.
@vinothkannans você pode corrigir a mensagem de erro aqui.
Por favor, forneça um valor para “XYZ”
ou seja,
Por favor, forneça um valor para “Setor”.
Podemos simplesmente escolher o primeiro campo obrigatório ausente.
Isso certamente teria ajudado no problema que tivemos ao tentar cadastrar um grande volume em um curto espaço de tempo, com campos de usuário excessivos. Obrigado por resolver isso.
A mensagem de erro correta foi adicionada agora no PR aberto abaixo
P.S. mesclado
