On 10/17/06, Michael Radziej <[EMAIL PROTECTED]> wrote: > What is the current policy? Should this output be xhtml conform > or not?
Policy for Django? There isn't one, so far as I know. Policy for the web in general? Good luck with that :) > The point is, and that goes above the csrf message, I don't know > if it's a good idea or not to use xhtml at all. You need to call > it text/html for IE6 and before, but to get any benefit from xml > (i.e., to see your errors immediately and get a more rigid > interpretation from the browser), you need to call it > application/xhtml+xml at least to the browser that understand it. > But then you get interesting effects on stylesheets and > JavaScript: stylesheets are also interpreted a little bit > differently (e.g., case matters with xhtml but not with html; > java script is expected to use the namespace stuff) I have this > under control for myself, but I really don't know if it's a good > idea to propose xhtml in general. I think XHTML is fine, so long as it's in the hands of someone who really knows how to use it. There aren't a whole lot of people like that, though, so I don't think XHTML is appropriate in most of the cases where it's used. Of course, I may be accused of bias :) -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
