Consider migrating to <input type="date" /> for Angular date selectors
Bug #1840782 reported by
Bill Erickson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Wishlist
|
Unassigned |
Bug Description
Evergreen 3.3
Originally discussed here:
http://
There is a general consensus so far that using the native browser date input in favor of the ng-bootstrap equivalent is a worthy goal. There remain some questions about usability and accessibility.
I've created a branch that migrates <eg-date-select /> so it may be used for review and comparison.
If we move forward with this, a separate LP for input type="time" would probably be in order.
Branch en route.
To post a comment you must log in.
Here's a branch:
https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ berick/ lp1840782- date-time- native- widgets
From the commit: ---
Migrate <eg-date-select> implementation from ng-bootstrap to the browser-native <input type="date"/> element.
Create a DateUtil class to package some common date transforms, etc.
'DOB' handling in FormatService leverages the new DateUtil class for generating a local date from Y/M/D and does so any time a simple Y/M/D value is passed, instead of limiting to 'DOB' values.
Sandbox example expanded to demonstrate date clearing and improve layout.