Then why can you have radio inputs with the same name? I thought the point of Flash forms was to map directly to HTML forms, of course with improvements also, but holding onto the way they work. I know that sounds like a simplistic view.
It's almost always the case that we use both radio and checkbox inputs to show related data with radio capturing one and checkbox capturing many. Are there any benefits with moving away from this? Flash groups radio inputs, why not checkboxes? If name maps to ID why not have a group attribute? Identifying a form element with a unique ID makes sense, but why have a way of grouping these form elements which can then be referered to by another ID? Have I missed the point with this? Ade -----Original Message----- From: Mike Nimer [mailto:[EMAIL PROTECTED] Sent: 24 February 2005 21:43 To: CF-Talk Subject: RE: cfinput question... The reason the names have to be unique is because flex requires each component to have a unique id (which I believe is something flash forces on flex). And since we are using Flex under the covers we have to follow their rules for what a movie is and how it's defined. ---nimer -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 22/02/2005 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:196429 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
