Re: HTML5 and XHTML5 documents

Hello Nils, > On 23 Aug 2018, at 19:33, Nils Fredrik Gjerull wrote: > > How can we move forward on supporting XML serialization of HTML5 (XHTML5)? > > When I created the pull-request I did not think it would be very > controversial. After all, the XML style of writing HTML has been used > for

Re: HTML5 and XHTML5 documents

Hi Nils. Tim's original advice still stands: > Have you tried creating custom widget templates for XHTML? > https://docs.djangoproject.com/en/stable/ref/forms/renderers/ Once you have widget templates in place, if there are particular issues you are facing we can consider them but the

Re: HTML5 and XHTML5 documents

How can we move forward on supporting XML serialization of HTML5 (XHTML5)? When I created the pull-request I did not think it would be very controversial. After all, the XML style of writing HTML has been used for years. I guess many are not aware that HTML5 comes in two flavors and it creates

Re: HTML5 and XHTML5 documents

Den 20. aug. 2018 11:32, skrev Nils Fredrik Gjerull: > XML > materialization of HTML5, and there is also the SGML-inspired version. I intended to write XML serialization :) -- Nils Fredrik Gjerull - "Ministry of Eternal Affairs" Computer Department ( Not an official

Re: HTML5 and XHTML5 documents

Den 17. aug. 2018 22:07, skrev James Bennett: > > If you're basing your understanding on browser support, you're not > doing XML/XHTML. You're doing "a thing that looks like XHTML and works > in my browser". Webstandards has and probably always will be defined by browser support. That's how the

Re: HTML5 and XHTML5 documents

> serve Django Admin as 'text/html', and let other apps choose for themselves. Yes, DEFAULT_CONTENT_TYPE is deprecated, so the admin (soon) should always return text/html, and other apps can choose for themselves. (see ticket #23908 ) I think django

Re: HTML5 and XHTML5 documents

On Fri, Aug 17, 2018 at 3:41 AM, Nils Fredrik Gjerull wrote: > > I am talking about being able to serve pages as application/xhtml+xml, > this is defined by browser support as is the SGML version of HTML5. I > hardly think XML version of HML5 is more ill-defined than the SGML > version. I am not

Re: HTML5 and XHTML5 documents

Den 17. aug. 2018 12:07, skrev James Bennett: > > XHTML5 itself is neither well-specified nor robust; the new elements > of HTML5 are more or less dumped by fiat into the old 1999/XHTML > namespace, but who's to say parsers will actually be aware of that? > Especially validating parsers? Can you

Re: HTML5 and XHTML5 documents

On Fri, Aug 17, 2018 at 1:50 AM, Nils Fredrik Gjerull wrote: > I still would like a technical answer to why not support both standards? > And again XHTML5 is HTML5 with valid XML syntax. So valid XHTML5 is > valid HTML5, so there is no problem for a framework to provide HTML5 it > should just be

Re: HTML5 and XHTML5 documents

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

Re: HTML5 and XHTML5 documents

On 08/17/2018 06:50 PM, Nils Fredrik Gjerull wrote: think, however, that it is more clear if we give it a value. By the way, the syntax is not new it is the old syntax from HTML4. I have spent quite some time cleaning up ill-formed HTML4. One of the more significant differences between the

Re: HTML5 and XHTML5 documents

Den 17. aug. 2018 10:04, skrev Carlton Gibson: > Only half-joking, the diff here makes me want to weep. For me, 150 > files and 1803 line changes is just too much to  > enforce something that is of minority appeal. The changes are simple. Use '/>' at end of self-closing tags and give all

Re: HTML5 and XHTML5 documents

Hi Nils. > ... and an issue (#29681), which was prematurely closed as wontfix. As per the when you already re-opened #29038 on this issue, there now needs to be a consensus here before we can (or will) consider a new ticket for this. That's not "premature" — it's just how the project

Re: HTML5 and XHTML5 documents

Den 13. aug. 2018 14:52, skrev Tim Graham: > Another discussion about HTML vs XHTML > is https://groups.google.com/d/topic/django-developers/EdwwxxqcKVU/discussion. > > I think if you want to use XHTML, Django should make is possible, but > as it seems the majority of projects use HTML5, I would

Re: HTML5 and XHTML5 documents

Another discussion about HTML vs XHTML is https://groups.google.com/d/topic/django-developers/EdwwxxqcKVU/discussion. I think if you want to use XHTML, Django should make is possible, but as it seems the majority of projects use HTML5, I would stick to that as the default. Have you tried

Re: HTML5 and XHTML5 documents

Den 12. aug. 2018 20:06, skrev Jon Dufresne: > Django started adopting HTML5 features since before 2.1. I found > changes as early as 1.11. From the release notes: > > https://docs.djangoproject.com/en/dev/releases/1.11/#miscellaneous Perhaps, but I have run my project on Django 2.0 without being

Re: HTML5 and XHTML5 documents

Django started adopting HTML5 features since before 2.1. I found changes as early as 1.11. From the release notes: https://docs.djangoproject.com/en/dev/releases/1.11/#miscellaneous > The checked and selected attribute rendered by form widgets now uses HTML5 boolean syntax rather than XHTML’s

Re: HTML5 and XHTML5 documents

Den 12. aug. 2018 12:20, skrev Adam Johnson: > You didn't pose an exact question in your message, but I guess it's > "Can Django officially support XHTML5?" Django has supported XHTML for years, so it came as a surprise to me that Django 2.1 broke it. So it is more like "Can Django continue to

Re: HTML5 and XHTML5 documents

You didn't pose an exact question in your message, but I guess it's "Can Django officially support XHTML5?" As it's a stricter subset of HTML5, it seems a valid idea. But at the same time, we need to be able to support it going forwards, with test coverage and knowledge that this is what we aim

HTML5 and XHTML5 documents

I write this because the latest release version of Django (2.1) broke my site. On my site I serve my html documents with the unusual, but perfectly valid, mimetype application/xhtml+xml. That is I tell the browser to parse my html documents as XML. I do this because I prefer the stricter parsing