Why? Just put it in a script block and let the js in the returned html populate the select box
-----Original Message----- From: jusmeig [mailto:jusm...@gmail.com] Sent: Monday, 24 August 2009 10:38 PM To: MooTools Users Subject: [Moo] Re: Dynamic Dropdownlists Hi guys, Almost have it working, just a little confused now by the following: var req = new Request.HTML({url:'http://www.w.come/myscript.php', onSuccess: function(html) { If I want to do something with the response html (how do I access it??) } In the function above I want to be able to split the string that is returned and then output dropdowns using the code u guys gave me above? Ho do I access the response? On Aug 24, 12:56 pm, nwhite <changereal...@gmail.com> wrote: > new Option isn't "bad", it just ugly to deal with. My biggest issue is the > handling of the explicit 2 parameters for the add method. FF, Safari require > it. IE, fails when its present. This mean wrapping it in a a try/catch. Like > I said the older DOM api doesn't mix with the new one in IE. so appendChild( > new Option) fails. > > selectBox.appendChild( new Element('option', {'value' : value > > }).appendText(text) ); > > solves all my issues. > > On Mon, Aug 24, 2009 at 4:21 AM, Thierry bela nanga <bna...@gmail.com>wrote: > > > I remember I had problem with utf-8 using the new Option in IE a very long > > time ago... > > > On Mon, Aug 24, 2009 at 12:04 PM, Steve Onnis <st...@cfcentral.com.au>wrote: > > >> 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-se... > > >> 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 > > > -- > >http://tbela99.blogspot.com/ > > > fax : (+33) 08 26 51 94 51
