[TAP5-58] Tapestry should be smarter about event handler methods refiring events with the same name

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Abandoned
• Affects Version/s: 5.0.15
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 19/Nov/07 21:00
• Updated: 23/Nov/11 19:06
• Resolved: 23/Nov/11 19:06

Description

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.