On Fri, Aug 21, 2020 at 1:31 PM Frédéric Donckels < frederic.donck...@gmail.com> wrote:
> I am indeed using Ajax fallback links. What could make the event handlers > not properly registered/firing? > Check for JavaScript errors in your browser DevTools > Console. Most probably the JavaScript click event event binding has failed for some reason. > > I'll check the Ajax response. > > On Fri, 21 Aug 2020 at 11:46, Bas Gooren <b...@iswd.nl> wrote: > > > Hi, > > > > It sounds like you are using Ajax fallback links, and the javascript > event > > handlers are not properly registered or firing. > > If that happens, the link is processed like a normal/non-ajax link. > > > > When you inspect the Ajax response when the list is refreshed, do you see > > “Wicket.Ajax.ajax” javascript calls? > > > > Met vriendelijke groet, > > Kind regards, > > > > Bas Gooren > > > > Op 21 augustus 2020 bij 11:16:01, Frédéric Donckels ( > > frederic.donck...@gmail.com) schreef: > > > > Hello, > > > > we are in the process of migrating from Wicket 7 to 8.9.0 and have a > > troubling issue. On one page, we have a list of elements. When we click > on > > an "Add Button", an ajax panel is modified in the page to add a new > > element > > in the list. When the "submit button" (ajax) is clicked, the list is > > refreshed (added to the ajax target). > > > > But the puzzling thing, now, is that the Ajax buttons, in the list, do > not > > have an ajax target when clicked (the optional is empty, and from what > > I've > > seen so far, the listener doesn't consider it has been called within an > > Ajax request). This only happens when the list has been refreshed, when > it > > is populated initially, the button triggers properly an ajax listener. > > > > > > And this didn't happen with the same code on Wicket 7. > > > > Is that a known issue? How can I investigate further? > > > > > > Regards > > > > >
