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 以下のエラーメッセージを修正してください。
“XYZ” の値を入力してください
つまり、
“Sector” の値を入力してください。
不足している必須フィールドの最初のものを取得するだけで大丈夫です。
それは、短時間に大量のユーザー登録を試みた際に発生していた問題、特にユーザー入力項目が多すぎたことによる問題を確実に解消したでしょう。ご対応いただき、ありがとうございます。
正しいエラーメッセージが以下の open PR に追加されました
追伸：マージ済み
