This is fixed too. Can you please check? Thanks Massimo
On May 15, 9:20 am, DenesL <[email protected]> wrote: > @mgbelisle > Nice solvers. > > @Massimo > web2py is (correctly IMO) building request.vars.field as a list from > the three INPUTs, so for consistency I would expect form.vars.field to > be an exact copy after accepts. There is nothing in the w3.org specs > against the use of equally named INPUT controls outside the scope of > checkboxes and radio buttons, but you can set it as a web2py > "restriction by design". > > My other comment was also geared towards consistency: > inp1=INPUT(_name='field') > inp2=INPUT(_name='field',_type='text') # as used in widgets > inp1.attributes > {'type':'text','value':None,'_name':'field'} > inp2.attributes > {'_type':'text','value':None,'_name':'field'} > I know that you internally manipulate 'type' and '_type' and the logic > has been working so far, but it just seems inconsistent. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
