You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Alberto Lepe <al...@gmail.com> on 2005/03/04 16:48:18 UTC
Is this a bug? (Form name)
I already posted this before, but with out answer...
In the following example:
<form jwcid="form" name="formName">
...
Tapestry will not erase the "name" property. It would display:
<form name="Form0" name="formName" ... >
causing many Javascript errors (Form0 is not recognized on Javascript).
Quoting the book of "Tapestry in Action" on page 78, said:
" Informal parameters can be unevaluated static values, such as for width, or
expressions, such as for alt. Some informal parameters are discarded so that
they don't conflict with attributes rendered directly by the component. "
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Is this a bug? (Form name)
Posted by Per Olesen <po...@nordija.com>.
Actually, Jacob is right, ... it is a bug.
http://issues.apache.org/jira/browse/TAPESTRY-285
On Friday 04 March 2005 17:30, Jacob von Eyben wrote:
> Hi,
>
> The 'problem' relies in the fact that the form component, doesn´t have any
> reserved parameters, hence it doesn't remove the name attribute you have
> in your mockup.
>
> One could say that it's a bug. I can't think of any reason why this should
> not be reserved.
>
> /Jacob
>
> > How does your .page specification define the "form" component? You are
> > specifying an informal parameter in your .html page, but you may or may
> > not also be supplying a "name" in your .page spec. If you want to leave
> > it all in the .html, this should work:
> >
> > <form jwcid="formName@Form">
> >
> > Shawn
> >
> > Quoting Alberto Lepe <al...@gmail.com>:
> >> I already posted this before, but with out answer...
> >> In the following example:
> >> <form jwcid="form" name="formName">
> >> ...
> >>
> >> Tapestry will not erase the "name" property. It would display:
> >> <form name="Form0" name="formName" ... >
> >>
> >> causing many Javascript errors (Form0 is not recognized on
> >> Javascript).
> >>
> >> Quoting the book of "Tapestry in Action" on page 78, said:
> >>
> >> " Informal parameters can be unevaluated static values, such as for
> >> width, or
> >> expressions, such as for alt. Some informal parameters are discarded
> >> so that
> >> they don't conflict with attributes rendered directly by the
> >> component. "
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail:
> >> tapestry-user-help@jakarta.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
--
Per Olesen @ Nordija A/S - www.nordija.com - main#: +45 70 20 25 10
email: polesen@nordija.com - cell#: +45 23 38 95 81
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Is this a bug? (Form name)
Posted by Jacob von Eyben <je...@nordija.dk>.
Hi,
The 'problem' relies in the fact that the form component, doesn´t have any
reserved parameters, hence it doesn't remove the name attribute you have
in your mockup.
One could say that it's a bug. I can't think of any reason why this should
not be reserved.
/Jacob
> How does your .page specification define the "form" component? You are
> specifying an informal parameter in your .html page, but you may or may
> not also be supplying a "name" in your .page spec. If you want to leave
> it all in the .html, this should work:
>
> <form jwcid="formName@Form">
>
> Shawn
>
>
> Quoting Alberto Lepe <al...@gmail.com>:
>
>> I already posted this before, but with out answer...
>> In the following example:
>> <form jwcid="form" name="formName">
>> ...
>>
>> Tapestry will not erase the "name" property. It would display:
>> <form name="Form0" name="formName" ... >
>>
>> causing many Javascript errors (Form0 is not recognized on
>> Javascript).
>>
>> Quoting the book of "Tapestry in Action" on page 78, said:
>>
>> " Informal parameters can be unevaluated static values, such as for
>> width, or
>> expressions, such as for alt. Some informal parameters are discarded
>> so that
>> they don't conflict with attributes rendered directly by the
>> component. "
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail:
>> tapestry-user-help@jakarta.apache.org
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Is this a bug? (Form name)
Posted by Shawn Church <sh...@boxity.com>.
How does your .page specification define the "form" component? You are
specifying an informal parameter in your .html page, but you may or may
not also be supplying a "name" in your .page spec. If you want to leave
it all in the .html, this should work:
<form jwcid="formName@Form">
Shawn
Quoting Alberto Lepe <al...@gmail.com>:
> I already posted this before, but with out answer...
> In the following example:
> <form jwcid="form" name="formName">
> ...
>
> Tapestry will not erase the "name" property. It would display:
> <form name="Form0" name="formName" ... >
>
> causing many Javascript errors (Form0 is not recognized on
> Javascript).
>
> Quoting the book of "Tapestry in Action" on page 78, said:
>
> " Informal parameters can be unevaluated static values, such as for
> width, or
> expressions, such as for alt. Some informal parameters are discarded
> so that
> they don't conflict with attributes rendered directly by the
> component. "
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org