On Fri, Nov 30, 2018 at 4:03 AM Christopher Dodunski < chrisfromtapes...@christopher.net.nz> wrote:
> That sounds promising Thiago. Does your component support time also, Nope, just date, but it could be copied and adapted to one who accepts time too. > or just date (you mentioned yyyy-mm-dd is hardcoded)? > It's hardcoded because that's the format used by the browsers when sending the selected date. The actual format presented to the users is locale-dependent. > I imagine others are using the existing DateField with success, whether > inside or outside of zones. Assuming the DatePicker javascript is using > AJAX to invoke a zone refresh, is there perhaps a way of disabling this > without meddling with the code? I had thought that without "async=true", > components would not invoke zone refreshes. > Not all components have that parameter. DatePicker doesn't trigger zone refreshes as far as I know. > > Regards, > > Chris. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Thiago
