James Bennett wrote: > So I've been poking around in the newforms code, and it appears that > the pre-defined widgets will be producing XHTML-style output.
I had the same thought but I wrote a quick test with an HTML 4 strict doc-type, put an input tag in it like this: <input type="text" name="mytext" />, and it was still valid. I'd like to see agnostic HTML from Django too, but if it isn't producing anything that breaks HTML 4, I'm happy. One of my worries is that the W3C, from what I've read, is going to re-invigorate HTML and work on HTML5 as well as XHTML2. If these two diverge enough, Django may need support for both. Somewhere I think I suggested the possibility of passing in a template string to the forms on how they should render, but the only purpose of this would be to remove the "/", and requires knowledge of the local variables. Last I looked the forms stuff is pretty flexible with adding attributes (ie: class names) and things. So there's not a lot of benefit doing that. -Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
