#23908: XHTML breaks admin site
-------------------------------+--------------------------------------
Reporter: brian | Owner: nobody
Type: Bug | Status: closed
Component: contrib.admin | Version: 1.7
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by brian):
Django Admin doesn't need to support XHTML, however it should be possible
to use it with applications that do use XHTML.
As it is, it is not possible for applications to support both XHTML 5 and
use Django Admin, because the DEFAULT_CONTENT_TYPE setting is global
across all of Django. So you either have to use HTML or turn off Django
Admin.
Not to mention XHTML being superior because parsing errors are flagged
immediately rather then being ignored.
The meta setting I previously gave would allow Django admin to work as
HTML even if the DEFAULT_CONTENT_TYPE setting has been changed, although
it could perhaps be argued this is a bit of a kludge, as it overrides the
HTTP headers.
--
Ticket URL: <https://code.djangoproject.com/ticket/23908#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.25af1e96fc1d21e0e84faf40445d7b1c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
