Hi Steve. We remembered why we did this: it's Webkit's fault. Or perhaps it is the fault of cgi.FieldStorage.
Even if you take FormKit out of the equation, a multiple-select <input> tag works this way. We can certainly "fix" this via FormKit, but we thought it bad to change the behavior of the way webkit handles submitted posts. But we agree with you; it SHOULD be consistent. It should ALWAYS be a list Thoughts, anyone? Should we fix this 'bug' or keep it consistent with WK? > > On Wed, 23 Feb 2005 14:13:58 -0500, Steve M <[EMAIL PROTECTED]> wrote: > > > But if one option was selected, f.value() is type string and is equal to > > > whatever was selected, whereas if more than one option was selected, > > > f.value() is type list, with members being strings for the options > > > selected. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
