Anonymous | Login | Signup for a new account | 2021-01-26 15:49 UTC | ![]() |
Main | My View | View Issues | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
0000926 | Amarillo | JavaScript & HTML | public | 2014-06-19 10:54 | 2014-06-19 10:54 | ||||||
Reporter | Fred | ||||||||||
Assigned To | Fred | ||||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||||
Status | assigned | Resolution | open | ||||||||
Platform | All | OS | All | OS Version | All | ||||||
Product Version | 0.1-SNAPSHOT | ||||||||||
Target Version | 0.2 | Fixed in Version | |||||||||
Summary | 0000926: Add client-side form validation and visible errors | ||||||||||
Description | As it stands it's possible to put non-URLs into the URL field and have them end up as relative paths in the final display page. Not very good, although the handler gracefully tells the user their path was dodgy, so that's OK. On the other hand, it'd be nice if we only ever had valid URLs end up in the database. Ditto for email addresses. And possibly other things, too. Some server side validation could also be done and errors returned if not good enough. For the time being, just be careful what we type in. | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | |||||||||||
Copyright © 2000 - 2011 MantisBT Group |