View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003195 | AJAX/JS | Feature Request - Interface | public | 2018-06-01 01:10 | 2018-06-01 20:23 |
| Reporter | Hinoe | Assigned To | DerIdiot | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | reopened | ||
| Summary | 0003195: Add input validation to forms where bad input causes blocking errors | ||||
| Description | For nearly every user, it is incredibly irritating to fill out detailed forms and be hit with a blocking error because ONE field had bad (illegal/mismatching/blank) input, because that forces the user to redo the hell out of everything, effectively duplicating all the work. As far as I can see, there are two solutions to this problem. One is to complain about the error as currently done, but return the form as submitted by the user rather than nothing. That is an okay solution, I suppose, but there is another which is better from an user experience perspective (and hopefully easier to implement), namely JS-based input validation. Basically, forms with fields that can complain about bad values should complain in advance where feasible (dates in particular), in the best interest of letting the user fix it without so much pain (and potentially figure out what the issue is if they don't know yet). | ||||
| Steps To Reproduce | 1. Make a ton of changes in some form that has a possible illegal input. 2. Add an illegal input. 3. Submit. 4. Make yourself taller. | ||||
| Additional Information | Related: https://anidb.net/perl-bin/animedb.pl?show=cmt&id=80958 | ||||
| Tags | No tags attached. | ||||
|
|
ahahahaaha this is a troll ticket right? right? ... do you even remotely understand the scope of this request? you expect to put _all_ validation logic into js. that is a metric ton and will easily diverge between the 2 codebases whena change is done. no will never happen. not of this scale anyway. touching up individual forms where it makes sense, maybe. general blanket appliance, hell no. |
|
|
Instead of the Ajax suggestion, can we instead have a "back to form" button on the error page, that will bring back the form but populate it with all of the user inputs so that you don't need to re-enter? |
|
|
But did you actually read the ticket? I explicitly provided another potential solution, which would be done entirely in perl, thereby solving literally every concern you raised in your reply. If this solution is hard to implement and that one isn't, I'll happily switch. I'll even write the ticket for it. With that said, what AniDB currently provides is its own in-house equivalent to the stupidity of PHP's error handling (T_PAAMAYIM_NEKUDOTAYIM, anyone?), and it's downright shocking a request to fix it would be dismissed as "a troll ticket". |
|
|
https://tracker.anidb.net/view.php?id=3197 I'd reclose this ticket, but I can't, so /shrug |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2018-06-01 01:10 | Hinoe | New Issue | |
| 2018-06-01 12:15 | DerIdiot | Assigned To | => DerIdiot |
| 2018-06-01 12:15 | DerIdiot | Status | new => closed |
| 2018-06-01 12:15 | DerIdiot | Resolution | open => won't fix |
| 2018-06-01 12:15 | DerIdiot | Note Added: 0004234 | |
| 2018-06-01 13:14 | CDB-Man | Note Added: 0004235 | |
| 2018-06-01 20:12 | Hinoe | Status | closed => feedback |
| 2018-06-01 20:12 | Hinoe | Resolution | won't fix => reopened |
| 2018-06-01 20:12 | Hinoe | Note Added: 0004236 | |
| 2018-06-01 20:20 | Hinoe | Note Added: 0004237 | |
| 2018-06-01 20:20 | Hinoe | Status | feedback => assigned |
| 2018-06-01 20:23 | DerIdiot | Status | assigned => closed |
