[
https://issues.apache.org/jira/browse/TAP5-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-1980:
---------------------------------
Labels: bulk-close-candidate (was: alert dismiss)
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.
> Support for dismissing a single alert
> -------------------------------------
>
> Key: TAP5-1980
> URL: https://issues.apache.org/jira/browse/TAP5-1980
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3.4
> Reporter: MatÃas Blasi
> Priority: Minor
> Labels: bulk-close-candidate
>
> It would be usefull to dismiss a single alert.
> Up to know there is no event triggered to the server if a single alert is
> dismissed. I have extended the AlertStorage, so I need to know when a single
> alert is dismissed in order to reflect that into my storage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
