Hi Bas,
Thank you for your reply. You're right: the order here changes
everything and the id is generated if I switch the elements.
It's confusing that the behaviour of wicket:for isn't consistant
depending on html elements order, in my opinion the order shouldn't
matter.
Best regards,
Virginie
Hi Virginie,
Looking through the wicket source code, I see that wicket:for is handled
through a component resolver (see AutoLabelResolver).
Since these are run at render time (see MarkupContainer#renderNext()) and
your label is after the checkbox in html, it means that your checkbox input
is
Hi there,
When we are using wicket:for into a PropertyListView, the id is not
automatically set on the related input, except if we force it by using
setOutputMarkupId(true).
Outside a propertyListView the id is generated without forcing it.
Please can you tell me if it's normal, if I use it
