#7452 closed New feature (wontfix)
Settings for HTML4 or XHTML output
Reported by: | Marc Fargas | Owned by: | nobody |
---|---|---|---|
Component: | Core (Other) | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Design decision needed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Not too long ago an issue was brought to django-developers this thread about using HTML4 or XHTML on the output generated inside Django.
It was said to:
- Leave this until 1.0 gets out
- Fill a ticket to not forget this and keep track.
- Find an elegant way to handle this.
So here it is. My first recomendation: have a setting for choosing either HTML4, XHTML, HTML5... etc.
Change History (10)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:3 by , 16 years ago
milestone: | → post-1.0 |
---|
comment:5 by , 14 years ago
Severity: | → Normal |
---|---|
Type: | → New feature |
comment:6 by , 13 years ago
Easy pickings: | unset |
---|---|
UI/UX: | unset |
See http://groups.google.com/group/django-developers/msg/a65fbbc8effcd914. As is pointed out there, having a setting to switch between HTML and XHTML would be very irritating - and besides, moving forward we'll probably want to stick to HTML5. Can we close this as wontfix?
comment:7 by , 13 years ago
Triage Stage: | Accepted → Design decision needed |
---|
comment:8 by , 13 years ago
Yes, I also think it's a WONTFIX now that all Django templates use HTML5.
comment:10 by , 8 years ago
"The web framework for perfectionists with deadlines." Maybe not everyone is using the same definition of perfection. =)
#6925 asks for something about that.