[jira] [Updated] (TAP5-1102) Customization of invocations / callbacks on the rowinjector trigger

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade updated TAP5-1102:
---------------------------------


This issue has been last updated about 1.5 years ago and has no information about the versions that are affected. That makes it hard to determine whether it is still relevant.
If the issue still persists with the current stable version (5.3.7) or the most recent development preview of Tapestry (5.4-beta-6), both of which are available from Maven Central, please update it as soon as possible, adding the respective version(s) to the issue's "Affects Version/s".

> 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.2#6252)