View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003558 | AniDB Website | Bug Report | public | 2023-05-14 18:08 | 2023-05-14 18:08 |
Reporter | thany2 | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Summary | 0003558: Registration procedure is too rough | ||||
Description | So I just registered. It worked, but only after getting slapped in the face a few times. 1. The username needs to be checked on the registration page, not after submitting the form. 2. This lead to an error that my username was already in use. That`s not my fault, so don`t punish me for it: 3. After going back, and trying another one, submitting the form lead to another error: wrong captcha response. I can`t do anything about that! the reCaptcha thing was already checked. I can`t uncheck and recheck it, and I had no way of knowing to do that even if it was possible! 4. Pressing F5 to satisfy the captcha thing, to recheck it, removes my e-mail and password confirmation box. But it did remember the username and first pasword box, curiously enough, Please make it so that pressing F5 doesn`t clear any fields. I think if you make it so that checking if everything is ok *before* submitting the form, submitting the form won`t result in an error (unless it`s something truly broken). It all comes down to not punishing a user for doing something that they have no way of knowing is incorrect. Especially in an onboarding procedure. Onboarding/registration is a very precious window of time where potential users will simply give up and go somewhere else if they can`t get it to work. Luckily I`m pretty tech-savvy and I knew to press F5. I would also suggest: 1. Don`t ask the user to confirm a password. It`s never been proven to solve any problem, and it`s basically trusting the user to copypaste their password correctly. 2. Don`t include a captcha that incorrectly fails after using the back button. The captcha should only *correctly* fail when the user has not responded ticking the checkbox. But when the checkbox is ticked and it still fails, it`s time to look for a better one. 3. Don`t have such strange requirements for password characters. It not only suggests that you`re storing passwords in your database and your database cannot handle those forbidden characters for some reason, it also defies security by reducing the number of different characters that can be allowed, and it interferes with Firefox`s own password generator. | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2023-05-14 18:08 | thany2 | New Issue |