tapestry-dev@jakarta.apache.org
[Top] [All Lists]

Re: Should Form component name parameter not be reserved?

Subject: Re: Should Form component name parameter not be reserved?
From: Mikaël Cluseau
Date: Tue, 15 Feb 2005 09:59:32 +0100
The name parameter is the same as the component's name (if you have only
one render of your Form). E.g. <form jwcid="xxx@Form"> will produce
<form name="xxx">.

Le dimanche 13 fÃvrier 2005 Ã 11:52 +0100, Per Olesen a Ãcrit :
> Hi,
> 
> I was wondering. The "Form" component documentation says that it takes 
> informal parameters and that it has no reserved parameters.
> 
> But Form component always emits a name="xxx" attribute on the resulting html 
> form tag, so should it not be reserved?
> 
> I had a concrete problem where I, in my templates had name="xxx" on my form 
> elements (as javascript in preview referenced it by name) but the forms 
> started failing in some browsers. This showed to be due to final html having 
> two name="xx" attributes, and js in one browser took one of them and js in 
> another browser took the other.
> 
> ?
> 
> Regards, Per
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: tapestry-dev-help@xxxxxxxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>