had a read of this....can you explain why new Option() is bad if it is still supported? With all the other option you has to mess around with it to get it to work. new Option() just works and always has so i dont see it being bad especially when you are dealing with older browsers
_____ From: nwhite [mailto:changereal...@gmail.com] Sent: Monday, 24 August 2009 8:44 PM To: mootools-users@googlegroups.com Subject: [Moo] Re: Dynamic Dropdownlists I wrote a post a while ago about the bugs/features surrounding dynamic population of a select form. http://www.propertymaps.com/blog/2008/04/10/dynamically-populating-select-el ements-with-javascript/ On Mon, Aug 24, 2009 at 3:23 AM, Steve Onnis <st...@cfcentral.com.au> wrote: selects are funny like that I would be using the JS to use new Option() to insert the options, not HTML like that. _____ From: Justin Meighan [mailto:jusm...@gmail.com] Sent: Monday, 24 August 2009 8:11 PM To: mootools-users@googlegroups.com Subject: [Moo] Dynamic Dropdownlists Hi guys, I'm using mootools to create some dynamic dropdownlists. Basically the user selects from a list, and the second list is dynamically populated. The way I have been trying to do it is as follows: 1. Onchange on list one I did a Request.HTML to a script that game me back the option values for list 2. I then injected the options into the id of my second list. It kind of works, but for some reason the list ony seems to have 1 item in it, despite there being 4-5 properly formed <option value="">blah</option> tags? Any ideas why it lists them all as just one option? Thanx Justin
