Re: Ajax - component not rendered.

2022-11-03 Thread Laurent Duparchy
Yes I corrected that HTML too. (which was auto-corrected by browsers I think, at least by Firefox). I looked for errors in Firefox debugger.  The console reports a warning then an error in a generated js : Warning : jQuery.Deferred exception: b is null

Re: Ajax - component not rendered.

2022-11-03 Thread Laurent Duparchy
Hi, good catch, but unfortunately removing that surrounding did not solve the problem. Checking the *generated *markup for   , I see that it is translated and the id is changed, so it does not seems to create a collision to use same wicket:id as another id, even though it may be confusing

Re: Ajax - component not rendered.

2022-11-03 Thread Sven Meier
That HTML doesn't look valid to me: Your THs belong inside a TR, and while you're at it move that one into a THEAD.     https://www.w3schools.com/tags/tag_th.asp Maybe this is just a problem with replacing the HTML in the browser, this is why I adviced you to check the response of the Ajax

Re: Ajax - component not rendered.

2022-11-03 Thread Dirk Forchel
Hi Laurent, I've noticed that you use the same markup ID 'wakeUpForm' twice. Maybe that's the reason for some Ajax problems. Dirk Am 28/10/2022 um 09:43 schrieb Laurent Duparchy: Hi, Sorry for the basic question If this is the wrong place to ask, please tell me. If there is a relevant

Re: Ajax - component not rendered.

2022-11-03 Thread Laurent Duparchy
You need more than that ?            ... *Laurent Duparchy ESRF - The European Synchrotron MIS Unit 04 76 88 22 56*