I've tried it out on both a browser that supports HTML5 date fields (Chrome) and a browser that doesn't (Firefox), and it seems to be working right, but I'm open for ideas on ways to do it better.The original patch expected a date/time string in the ISO form as a default value for the form, but it has been altered so that you now pass a Drupal Date Time object as the default value instead of a date string.

Since this is a regular form element type, it can be used by any form, not just as a Field module field.

So I've switched the node and comment creation dates to use it.

This makes the node and comment creation dates HTML5-compatible, and provides the j Query datepicker as a fallback for browsers that don't support the HTML5 widgets. It's as simple as I can make it and still provide something useful.

This is an element that splits the field into a 'date' and a 'time'.

The element handles its own validation and manages the explosion of a date into date and time parts, and the transformation of the user input back into a date, so adding it to a form is pretty simple.

Each of those parts is constructed to be HTML5-compatible.Since the support for HTML5 date and time is horrible (missing on most desktop browsers), the j Query datepicker is provided as a fallback for the 'date' field by testing to see if the HTML5 date is supported and providing the datepicker if it is not.Dates are an important data type for a lot of different websites.We might not need all the complexity that the date module can currently handle (repeating dates, etc), but we should at least be able to handle a simple "Date of birth" field out of the box.Dries expressed his interest in having date fields in Drupal 7 (The patch adds a new form element type called 'datetime'.