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.
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.
That would certainly have helped the problem we had trying to sign up a load in a short space of time with way too many user fields. Thanks for addressing it.