[T5.2] Name property doesn't match id or is missing

2010-09-09 Thread Blower, Andy
We're upgrading from tapestry 5.1 to 5.2 and have spotted some strange things 
with the name property of various components. Tapestry forms no longer include 
the name property at all. Other elements such as the tapestry select component 
used to have matching id and name properties and now they seem to have 
different values. Does anyone know if these change are intentional and the 
reason behind them? Here's an example of the old select box rendered in 5.1 and 
then in 5.2:

select title=Select a day id=select name=select

select title=Select a day id=select name=select_0



Name property doesn't match id or is missing

2010-09-09 Thread matt.f...@proquest.co.uk

We're just upgrading from tapestry 5.1 to 5.2 and have spotted some strange
things with the name property of various components. Firstly tapestry forms
no longer include the name property at all. Other elements such as the
tapestry select component used to have matching id and name properties and
now they seems to have different values. Does anyone know if these change
are intentional and the reason behind them? Here's an example of the old
select box rendered in 5.1 and then in 5.2: 

select title=Select a day id=select name=select

select title=Select a day id=select name=select_0
-- 
View this message in context: 
http://tapestry.1045711.n5.nabble.com/Name-property-doesn-t-match-id-or-is-missing-tp2827101p2827101.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: [T5.2] Name property doesn't match id or is missing

2010-09-09 Thread Howard Lewis Ship
Just answered this in a separate thread.

On Thu, Sep 9, 2010 at 2:39 AM, Blower, Andy andy.blo...@proquest.co.uk wrote:
 We're upgrading from tapestry 5.1 to 5.2 and have spotted some strange things 
 with the name property of various components. Tapestry forms no longer 
 include the name property at all. Other elements such as the tapestry select 
 component used to have matching id and name properties and now they seem to 
 have different values. Does anyone know if these change are intentional and 
 the reason behind them? Here's an example of the old select box rendered in 
 5.1 and then in 5.2:

 select title=Select a day id=select name=select

 select title=Select a day id=select name=select_0





-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org