> If you don't mind my asking, why were tables chosen? I think, because that was the quickest way to implement.
> They don't follow > the proper structure of a form... as far as I could tell from the > source, the form element isn't used at all; I'm surprised the forms > even function. > > I'm somewhat new to web.py and I enjoy it so far, but this sort of > rendering bugged me. If you want, I could see about modifying form.py > to adhere to W3C standards. In its current form (no pun intended :P), > it will not validate with w3's validator, and may not render properly > in all browsers. Yes, form.py deserves a complete overhaul. -- You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en.
