tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Andreou (JIRA)" <...@tapestry.apache.org>
Subject [jira] Updated: (TAPESTRY-1982) Autocompleter should offer an allowCache parameter (currently caching is enabled by default with no way to disable it)
Date Sun, 09 Mar 2008 08:41:46 GMT

     [ https://issues.apache.org/jira/browse/TAPESTRY-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andreas Andreou updated TAPESTRY-1982:

    Fix Version/s: 4.1.6

> Autocompleter should offer an allowCache parameter (currently caching is enabled by default
with no way to disable it)
> ----------------------------------------------------------------------------------------------------------------------
>                 Key: TAPESTRY-1982
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1982
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: 4.1.5
>            Reporter: I D
>            Priority: Minor
>             Fix For: 4.1.6
> The dojo component that underlies the Autocompleter component - Select - has an "allowCache"
property, which is set to true by default.
> This means that even when working in "remote" mode, results are cached locally after
they have been fetched for the first time. This can be a problem. Consider the following scenario:
> A registration form has a PropertySelection component for country of residence and an
Autocompleter component for city of residence. As soon as a country is changed, the Autocompleter
model is aynchronously altered so as to match cities only from the selected country. A user
first selects country "UK" for example, and then types "lon" into the city field. Some suggestions
of city names are then retrieved from the model. The user then changes the country (e.g. after
realizing he chose the wrong country) and types the same string into the city field again.
Unfortunately the model will not even be polled this time, since dojo chaches the results
that were extracted the last time the same filter was used.
> The Autocompleter component should therefore offer an allowCache parameter that would
be copied to the dojo.widget.Select.allowCache property on initialization.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message