[jira] [Commented] (WICKET-4764) Ajax links on second page of datatable not working if client side filtering is active

["Carsten Behring (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489036#comment-13489036 ] 

Carsten Behring commented on WICKET-4764:
-----------------------------------------

I would like to reopen this problem.
let me try to explain, what situation I have.

I have an html table my page, which has one column with ajax links.

This table is sorted /paginated and filtered on client side via the jquery datatable component.

This leads to the fact that only a subset of table rows are shown/present on page load. The other rows are removed via client side java script from the dom by the datatable jquery component.

So now the wicket ajax supports adds on click events only to the VISIBLE/present rows (but not to all rows).
If I now change the visible rows client side, new rows become visible, without having event handlers added to them.

So clicking those new rows does not do anything.

I get error messages in the Ajax debug window like this:
ERROR: Cannot find element with id: statusLink1a6
ERROR: Cannot find element with id: statusLink1a7
....

Regards,

Carsten 


                
> Ajax links on second page of  datatable not working if client side filtering is active
> --------------------------------------------------------------------------------------
>
>                 Key: WICKET-4764
>                 URL: https://issues.apache.org/jira/browse/WICKET-4764
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 6.0.0
>            Reporter: Carsten Behring
>
> I am using jquery datatable with wicket 6.0.0.
> One of my columns contains an ajax link, which opens a ModalDialog.
> From wicket 6.0.0 onwards, the links do only work on the first page of the paginated list.
> (The list is client side paginated by jquery datatable)
> There is the same problem, if the list gets filtered (client side).
> It seems to me that there is a problem with the Ajax links, as soon as some of the rows are "invisible" (because filtered or on other page)
> It seems that the ajax events are either not fired at all, or do not manage to call the server side "onClick" method.
> With wicket 1.5.8 everything was working.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira