You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Fritz Pröbstle (JIRA)" <de...@tapestry.apache.org> on 2008/07/15 12:05:31 UTC
[jira] Updated: (TAPESTRY-2520) (Select) - Event Bubbling - No
chance to handle more submit buttons from the component in the container
[ https://issues.apache.org/jira/browse/TAPESTRY-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fritz Pröbstle updated TAPESTRY-2520:
-------------------------------------
Description:
I have an address component addcomp.tml with has 2 submit buttons with t:id="add" and t:id"remove".
I add this component (with t:id=" addcomp" ) to my Page address.tml .
Now the page should handle the following events (pseude code)
@Event(component=" addcomp.add") onSelectedFromAdd() and
@Event(component=" addcomp.remove") onSelectedFromRemove() .
But the tap5 gives me only the change to hande
@Event(component=" addcomp") onSelectedFromAddcomp ()
in the page(container) code -I can get chance to handle the add and remove event individually.
My Proposual:
Allow something like:
@Event(component=" addcomp.add") onSelectedFromAddcomp_Add() and
@Event(component=" addcomp.remove") onSelectedFrom Addcomp_Remove() .
This may be not a really bug (there are workarounds) but this workarounds may produce awksome code.
I wouls like to have an "Event-Bubble solution " for this issue
was:
I have an address component addcomp.tml with has 2 submit buttons with t:id="add" and t:id"remove".
I add this component (with t:id=" addcomp" ) to my Page address.tml .
Now the page should handle the following events (pseude code)
@Event(component=" addcomp.add") onSelectedFromAdd() and
@Event(component=" addcomp.remove") onSelectedFromRemove() .
But the tap5 gives me only the change to hande
@Event(component=" addcomp") onSelectedFromAddcomp ()
in the page(container) code -I can get chance to handle the add and remove event individually.
My Proposual:
Allow something like:
@Event(component=" addcomp.add") onSelectedFromAddcomp_Add() and
@Event(component=" addcomp.remove") onSelectedFrom Addcomp_Remove() .
> (Select) - Event Bubbling - No chance to handle more submit buttons from the component in the container
> -------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2520
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2520
> Project: Tapestry
> Issue Type: Bug
> Affects Versions: 5.0.13
> Reporter: Fritz Pröbstle
>
> I have an address component addcomp.tml with has 2 submit buttons with t:id="add" and t:id"remove".
> I add this component (with t:id=" addcomp" ) to my Page address.tml .
> Now the page should handle the following events (pseude code)
> @Event(component=" addcomp.add") onSelectedFromAdd() and
> @Event(component=" addcomp.remove") onSelectedFromRemove() .
> But the tap5 gives me only the change to hande
> @Event(component=" addcomp") onSelectedFromAddcomp ()
> in the page(container) code -I can get chance to handle the add and remove event individually.
> My Proposual:
> Allow something like:
> @Event(component=" addcomp.add") onSelectedFromAddcomp_Add() and
> @Event(component=" addcomp.remove") onSelectedFrom Addcomp_Remove() .
> This may be not a really bug (there are workarounds) but this workarounds may produce awksome code.
> I wouls like to have an "Event-Bubble solution " for this issue
--
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