| Summary: | Accessibility: Make it possible to enter date for restriction without using the datepicker widget | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Katrin Fischer <katrin.fischer> |
| Component: | Templates | Assignee: | Owen Leonard <oleonard> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
| Severity: | normal | ||
| Priority: | P5 - low | CC: | cbrannon, jonathan.druart, veron |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4402 | ||
| Change sponsored?: | --- | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Attachments: | Bug 11448: Remove readonly on datepicker - request.pl | ||
|
Description
Katrin Fischer
2013-12-26 10:37:44 UTC
Here are at least 3 places I've found that do not allow manual entry: request.pl opac-reserve.pl opac-memberentry.pl Christopher Created attachment 38427 [details] [review] Bug 11448: Remove readonly on datepicker - request.pl So... We have this solution (see patch), it's easy but there is no check on the date format. If you submit the form with a wrong date, you get the ugly software error message. What's better? Wait to have a system to catch dates not correctly formatted or go for this method for the moment? (In reply to Jonathan Druart from comment #3) > So... > We have this solution (see patch), it's easy but there is no check on the > date format. > If you submit the form with a wrong date, you get the ugly software error > message. > > What's better? Wait to have a system to catch dates not correctly formatted > or go for this method for the moment? This would be a step backwards. Is there no way to implement validation after key up or on submit? We use jquery validation for patron account entry that prevents submission until validation errors are corrected. Christopher (In reply to Christopher Brannon from comment #4) I suggestion a global solution on bug 14060. Actually I should have submitted it here. *** This bug has been marked as a duplicate of bug 14060 *** |