[
https://issues.apache.org/jira/browse/TAP5-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-1666:
---------------------------------
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.
> Mention how components can trigger custom events in the documentation page
> for Component Events
> ------------------------------------------------------------------------------------------------
>
> Key: TAP5-1666
> URL: https://issues.apache.org/jira/browse/TAP5-1666
> Project: Tapestry 5
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 5.3, 5.2
> Reporter: Chris Poulsen
> Priority: Minor
> Labels: bulk-close-candidate
>
> The "Component Events" page
> (http://tapestry.apache.org/component-events.html) should be extended to
> mention how components can trigger custom events using either event parameter
> of nested components or programmatically using ComponentResources.triggerEvent
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
