I have solved my issue with the cascading of SELECTs, by: - using a default value - clearing the bottom-level select with jQuery
You can see my code here: https://github.com/gonvaled/web2py-tests I hope that this will be easy to integrate with the rest of my application. On Thursday, August 30, 2012 8:01:31 PM UTC+2, Derek wrote: > > So so so many requests, please make this a default feature.... > > On Wednesday, August 29, 2012 7:09:43 AM UTC-7, Anthony wrote: >> >> This is a very frequent request -- we should probably have some built in >> functionality to handle this. In the meantime, check out >> http://stackoverflow.com/questions/8146260/best-practice-for-populating-dropdown-based-on-other-dropdown-selection-in-web2p/8152910#8152910 >> for >> some ideas. >> >> Anthony >> >> On Wednesday, August 29, 2012 9:59:37 AM UTC-4, Daniel Gonzalez wrote: >>> >>> Hi, >>> >>> I have a very common situation. The user has to choose a country and a >>> city. For both fields, I am using a select component. >>> The possible choices in the city component depend on what the user has >>> selected in the country component. >>> So what I would like to do is: >>> >>> 1. The user selects the country >>> 2. The cities component gets updated with data from the server >>> (web2py), *without* reloading the whole form. >>> 3. The user selects the city >>> 4. The form is submitted. >>> >>> I have no idea how to implement step 2. Could somebody comment? >>> >>> Thanks >>> Daniel >>> >> --
