Re: DateField behaviour when within a zone

On Sun, Dec 2, 2018 at 9:16 AM Christopher Dodunski <
[email protected]> wrote:

> > 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.


Yes, DateField uses AJAX, but not zones, so, if a DateField is causing an
AJAX update, that's definitely a problem there.


> Tomorrow I may delve into how "async=true"
> works when zones are nested.  I assume nested zones are allowable?
>

Yes, nested zones are allowed.


>
> Regards,
>
> Chris.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

-- 
Thiago