[jira] Updated: (TAP5-58) Tapestry should be smarter about event handler methods refiring events with the same name

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

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

Howard M. Lewis Ship updated TAP5-58:
-------------------------------------

    Issue Type: Improvement  (was: Bug)

> Tapestry should be smarter about event handler methods refiring events with the same name
> -----------------------------------------------------------------------------------------
>
>                 Key: TAP5-58
>                 URL: https://issues.apache.org/jira/browse/TAP5-58
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>
> An idiom that's evolving is for a component or mixin to receive an event via an event handler method, and then refire the event with a different context to obtain information or behavior from its container.
> Currently, you must either a) fire a differently named event or b) expressly trigger the event on the container's resources.
> It would be nice if Tapestry was smarter, and woul track which event(s) a component or mixin is currently handling, and would automatically skip the component if another event of the same name was triggered.  Basically, roll the b) logic above directly into ComponentResources/ComponentPageElement.

-- 
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