Denis Gervalle wrote:
> Sergiu,
>
> Do you means that this trick is used because the save action of XWiki
> is unaware of the list of field shown to the user by the preceding
> inline action, and you do not know if a field should be updated or
> left unchanged when it is not sent back ?
>
Denis Gervalle wrote:
> Sergiu,
>
> Do you means that this trick is used because the save action of XWiki
> is unaware of the list of field shown to the user by the preceding
> inline action, and you do not know if a field should be updated or
> left unchanged when it is not sent back ?
Exa
Sergiu,
Do you means that this trick is used because the save action of XWiki
is unaware of the list of field shown to the user by the preceding
inline action, and you do not know if a field should be updated or
left unchanged when it is not sent back ?
Denis
On 23 sept. 08, at 18:54, Serg
Denis Gervalle wrote:
> Hi all,
>
> Does anyone here knows why displayEdit of ListClass fields with a
> display type of checkbox, radiobutton or select is always followed
> with a hidden input tag, having the same name than the visible control ?
>
> Here is an excerpt of the source code that
Hi all,
Does anyone here knows why displayEdit of ListClass fields with a
display type of checkbox, radiobutton or select is always followed
with a hidden input tag, having the same name than the visible control ?
Here is an excerpt of the source code that cause this :
if (!getDispla
