[
https://issues.apache.org/jira/browse/TAP5-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade closed TAP5-1102.
--------------------------------
Resolution: Invalid
We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the
latest 5.4 preview release), feel free to provide the necessary information and
reopen.
> Customization of invocations / callbacks on the rowinjector trigger
> --------------------------------------------------------------------
>
> Key: TAP5-1102
> URL: https://issues.apache.org/jira/browse/TAP5-1102
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Peter Stavrinides
> Priority: Minor
>
> It could be made easier to customize invocations on the rowinjector trigger
> using JavaScript, at the moment its harder than it should be and limited to
> the click event.
> Robert Zeigler Wrote:
> It might be a nifty change to enable a second form of the "addAddRowTrigger"
> that takes, say, a js callback name as a 2nd argument. Or perhaps some flag
> triggering whether the first argument is an id or a callback. In any event,
> the initializer could then check for the appropriate condition, and if the
> condition is met, the initializer would delegate the setup to the callback,
> passing in the row injector, rather than assuming a click. If there's
> enough interest in something like this, I would be willing to do the work to
> add it to the framework (the exact api would need to be worked out, though).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
