Hi David,
We've sorted it out now. What I had before was
<p class="lift:find_user?form=POST">
<user:email-address/>
<user:submit/>
</p>
which produced
<form method="POST">
<p>
<input ...>
<input ...>
</p>
</form>
And we changed this to:
<form method="POST" class="lift:find_user">
<span class="email-address"/>
<span class="submit"/>
</form>
which produced
<form method="POST">
<input ...>
<input ...>
</form>
Thanks for the response, and sorry for the lack of information, that
was me trying to get out of the office to avoid the tube strike.
Cheers
Robbie
> On Wed, Nov 3, 2010 at 10:43 AM, Robbie Clutton <
robert.clut...@gmail.com>wrote:
>
>
>
> > Hi,
>
> > I've been trying out the new css style selectors with a form and I
> > noticed that if I had a 'p' element and used a lift form element in
> > the class attribute it pushed the form above the 'p' element, which is
> > fine. But when I used a 'form' element (instead of 'p') I had a form
> > within a form. Just thought it might be nice if the framework
> > recognised that and used that current form, therefor only outputting
> > one form.
>
> > Hope that makes sense.
>
> > Cheers
>
> > Robbie
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Lift" group.
> > To post to this group, send email to
lif...@googlegroups.com.
> > To unsubscribe from this group, send email to
> >
liftweb+u...@googlegroups.com<
liftweb%2Bunsu...@googlegroups.com>
> > .
> Beginning Scalahttp://
www.apress.com/book/view/1430219890