[jira] [Updated] (TAP5-1640) Introduce a way to define a custom duration for alert messages that have Duration.TRANSIENT

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade updated TAP5-1640:
---------------------------------
    Labels: bulk-close-candidate  (was: )

This issue affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent version of Tapestry (currently 5.4.0, available from Maven Central), please update it as soon as possible and add '5.4.0') to the issue's affected versions.

> Introduce a way to define a custom duration for alert messages that have Duration.TRANSIENT
> -------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1640
>                 URL: https://issues.apache.org/jira/browse/TAP5-1640
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.3
>            Reporter: Dusko Jovanovski
>            Assignee: Robert Zeigler
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> Introduce a way to define a custom duration for alert messages that have Duration.TRANSIENT.
> The best solution would be to enable setting the duration for each transient message, and to be able to override the currently hardcoded default duration of 15000ms.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)