You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Cédric BOONE (Jira)" <ji...@apache.org> on 2021/09/29 12:58:00 UTC
[jira] [Updated] (TAP5-2693) Grid and linksubmit context, defer is
not working
[ https://issues.apache.org/jira/browse/TAP5-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cédric BOONE updated TAP5-2693:
-------------------------------
Description:
Hello,
with a simple code :
TML:
<t:grid .... t:add="action" >
<p:actionCell>
<t:LinkSubmit t:id="edit" t:context="someContext" t:defer="false" >
.....
</t:LinkSubmit>
</p:actionCell>
</t:grid>
JAVA:
public void onSelectedFromEdit(String someContext){
// the value of someContext is always the last row context
}
the defer parameter should fix this, but it doesn't.
I know there is an open issue from 2017, but it hasn't been active since then.
was:
Hello,
with a simple code :
TML:
<t:grid .... t:add="action" >
<p:actionCell>
<t:LinkSubmit t:id="edit" t:context="someContext" t:defer="false" >
.....
</t:LinkSubmit>
</p:actionCell>
</t:grid>
JAVA:
public void onSelectedFromEdit(String someContext) {
// the value of someContext is always the last row context
}
the defer parameter should fix this, but it doesn't.
I know there is an open issue from 2017, but it hasn't been active since then.
> Grid and linksubmit context, defer is not working
> -------------------------------------------------
>
> Key: TAP5-2693
> URL: https://issues.apache.org/jira/browse/TAP5-2693
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.7.2
> Reporter: Cédric BOONE
> Priority: Major
>
> Hello,
>
> with a simple code :
>
> TML:
> <t:grid .... t:add="action" >
> <p:actionCell>
> <t:LinkSubmit t:id="edit" t:context="someContext" t:defer="false" >
> .....
> </t:LinkSubmit>
> </p:actionCell>
> </t:grid>
>
> JAVA:
>
> public void onSelectedFromEdit(String someContext){
> // the value of someContext is always the last row context
> }
>
> the defer parameter should fix this, but it doesn't.
>
> I know there is an open issue from 2017, but it hasn't been active since then.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)