I'm still waiting for my bosses to release the Html5DateField we have in our projects . . .
On Thu, Dec 6, 2018 at 9:44 PM Christopher Dodunski < chrisfromtapes...@christopher.net.nz> wrote: > 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 the existing DateField component, as there would be no need > for server round trips to wire the field and picker. Dates would be > formatted and parsed on component rendering and submission only. > > What do you think? > > Regards, > > Chris. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Thiago
