Bug 11448 - Accessibility: Make it possible to enter date for restriction without using the datepicker widget
Summary: Accessibility: Make it possible to enter date for restriction without using t...
Status: RESOLVED DUPLICATE of bug 14060
Alias: None
Product: Koha
Classification: Unclassified
Component: Templates (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-26 10:37 UTC by Katrin Fischer
Modified: 2015-04-27 08:47 UTC (History)
3 users (show)

See Also:
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 (1.43 KB, patch)
2015-04-23 15:21 UTC, Jonathan Druart 		Details | Diff | Splinter Review
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Katrin Fischer 2013-12-26 10:37:44 UTC 
For better accessibility it should be possible to enter the restriction date directly without being forced to use the datepicker widget.
Comment 1 Christopher Brannon 2013-12-30 15:52:06 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
Comment 2 Jonathan Druart 2015-04-23 15:21:00 UTC 
Created attachment 38427 [details] [review]
Bug 11448: Remove readonly on datepicker - request.pl
Comment 3 Jonathan Druart 2015-04-23 15:23:43 UTC 
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?
Comment 4 Christopher Brannon 2015-04-23 15:35:17 UTC 
(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
Comment 5 Jonathan Druart 2015-04-27 08:47:47 UTC 
(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 ***