Thanks Chris.
What puzzled me about the absent closing tag is that it appears
in the first example above, but not the second. Yet this markup is
generated by the same DateField component (line 276 to be precise:
"writer.end()").
I searched the web for alternative 'date pickers'. Bootstrap
On second thoughts, producing a new DateTimeField component is probably
wiser.
I'm impressed by the HTML5 "datetime-local" input type. Browsers that
don't support it should gracefully degrade to plain textfield.
A DateTimeField component based on this HTML5 element would be lighter
weight than
Hi
is valid html, while is valid xhtml, so depending on what
you are outputting open may be appropriate.
If the built-in datepicker is giving you grief, roll your own... I find
that we (at work) eventually have had to replace almost all of the slightly
fancy "gui" components in tapestry,
