I agree with Maxim, but I do not know the side effects, im going to try
it.. As it is now (out of the box), we cannot have nested forms in tables
(for example on form per <tr>) without breaking html.
-Nino
On Wed, Apr 24, 2019 at 3:24 AM Maxim Solodovnik <solomax...@gmail.com>
wrote:
> I would say we can create overridable method so users can specify which tag
> to use
> it will help with `<tr>`
>
> On Wed, 24 Apr 2019 at 01:39, Sven Meier <s...@meiers.net> wrote:
>
> > Hi,
> >
> > I think we could improve nested Forms so that only <form> tags are
> > turned into a <div>, but anything else stays as it is.
> >
> > WDYT?
> > Sven
> >
> > Am 23.04.19 um 10:01 schrieb nino martinez wael:
> > > Hi
> > >
> > > When nesting forms, the form tag are changed to an div and it is hard
> > coded:
> > > org/apache/wicket/markup/html/form/Form.java:1597
> > > ...
> > >
> > > tag.setName("div");
> > >
> > > ...
> > >
> > > If only I could change the tag to be tr, it would produce valid html.
> Are
> > > it deliberate to be hardcoded?
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
> --
> WBR
> Maxim aka solomax
>
--
Best regards / Med venlig hilsen
Nino Martinez
