>> 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. According to the Tapestry docs for DateField: "One wierd aspect here is that, because client-side JavaScript formatting and parsing is so limited, we (currently) use Ajax to send the user's input to the server for parsing (before raising the popup) and formatting (after closing the popup). Weird and inefficient, but easier than writing client-side JavaScript for that purpose." Seemingly the serverside formatting is failing, and a container's zone is getting refreshed instead. Tomorrow I may delve into how "async=true" works when zones are nested. I assume nested zones are allowable? Regards, Chris. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
