No, I think I was wrong - according to the clientChange documentation what you’ve got there should be ok, since the ‘live’ option defaults to true.
One thing, maybe - do you need to give each button a unique id for the live binding to work - I can’t see how a live binding can work without a selector that allows it to find the button when it is replaced.
Perhaps you would be better off just giving the button a class, without any ajax, then using delegate to bind to all buttons of that class after your widget (which is better jquery coding practice anyway).
Looking at that, I presume you have 5 items per page.
If you’re just changing pages through ajax and finding that the button then doesn’t work, you’ll need to look at the id assigned to the buttons (since you can see that is how it does the delegation).
I do not have five items per page. what I showed you the page’s source code after I inserted a row. it is also the newly inserted row. the row is inserted through the display of a dialog form which in turn makes an ajax call.
if I change the page using ajax and then pressed again the same button, it works.
Then suggest to create a js function to switch the task to make the ajax request if I understand correctly?