Den 17. aug. 2018 11:01, skrev Curtis Maloney: > One of the more significant differences between the advent of XHTML > and now, is that HTML5 introduced standard rules for how to deal with > "invalid" markup, meaning its handling in browsers became consistent. > > XHTML was a great move to allow a shift to browsers only accepting > valid markup, but it never happened -- in part because IE just > wouldn't play along.
IE now supports XHTML, so now it seams to me the biggest stumbling block is fashion. I cannot shake of the feeling that the arguments are "I don't like giving attributes a value and ending self-closing tags with '/>'" or perhaps "some engineer at Google says so". > So a softer solution was found - moving to HTML5 with defined failure > modes and handling. > > Currently, ISTM the only thing standing in the way of you using Django > for generating valid XHTML is the form widgets, in which case I > suspect writing your own widget templates would be far less work for > everyone involved. > > You could also provide them, quite trivially, as a 3rd party app for > other people facing the same issues as you. I suppose I could, but why? When giving attributes values and ending self-closing tags with '/>' makes it work for both cases? I really like Django with it excellent documentation and promotion of good practices. I newcomer can learn a lot from how Django is made. Django has provided valid XHTML markup for years, as far as I can tell. I can update the pull-request and concentrate the changes on the actual HTML generated by Django, and leave out the documentation and comments if it helps to make it more palatable. However, I think it would be a good thing to learn that there is a thing called XHTML5. Perhaps I can update the documentation to make it clear, but give the examples using the SGML syntax of HTML5? Regards -- Nils Fredrik Gjerull ----------------------------- "Ministry of Eternal Affairs" Computer Department ( Not an official title :) ) -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/18954a92-fa91-549e-91be-d6cdd5ab9c66%40gjerull.net. For more options, visit https://groups.google.com/d/optout.
