Hello, While going through my project output pages and validating them as "XHTML 1.0 Strict" I've learnt that SQLFORM creates a form with a table containing the DB labels and DB form elements, which is XHTML compliant up to that point. What fails the validation are the "_formkey" and "_formname" input fields that fall outside the table, placed just before the form's closing tag.
May I propose to create an additional row for the hidden elements and thus keep them bundled with the rest of the form content? That ensures XHTML compliance. (Tested) While at it, there is another issue: the "action" attribute is by default blank (invalid XHTML). Here I'd suggest that the forms use e.g. URL(r = request) as a devault value, instead of the blank string. This would not upset the existing concept - the programmer would be able to pass a custom "_action" just as before. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
