You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/05/30 13:35:09 UTC

[jira] [Updated] (TAP5-1986) Progressive display ignores application defaults for zone update effect

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

Jochen Kemnade updated TAP5-1986:
---------------------------------


This issue has been last updated about 1.5 years ago and has no information about the versions that are affected. That makes it hard to determine whether it is still relevant.
If the issue still persists with the current stable version (5.3.7) or the most recent development preview of Tapestry (5.4-beta-6), both of which are available from Maven Central, please update it as soon as possible, adding the respective version(s) to the issue's "Affects Version/s".

> Progressive display ignores application defaults for zone update effect
> -----------------------------------------------------------------------
>
>                 Key: TAP5-1986
>                 URL: https://issues.apache.org/jira/browse/TAP5-1986
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>            Reporter: Christoph Stichlberger
>            Priority: Minor
>
> The progressive display has no global default for the "update" parameter that is used for zone updates.
> Because of this, the zone update of progressive displays can't be customized using the application defaults, and has to be specified in every place it's used.
> It probably should use the same default as the zone for its update parameter:
> value = BindingConstants.SYMBOL + ":" + ComponentParameterConstants.ZONE_UPDATE_METHOD



--
This message was sent by Atlassian JIRA
(v6.2#6252)