Opened 7 years ago

Closed 4 years ago

#7452 closed New feature (wontfix)

Settings for HTML4 or XHTML output

Reported by: telenieko Owned by: nobody
Component: Core (Other) Version: master
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 (9)

comment:1 Changed 7 years ago by telenieko

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

#6925 asks for something about that.

comment:2 Changed 7 years ago by telenieko

  • Triage Stage changed from Unreviewed to Accepted

comment:3 Changed 7 years ago by garcia_marc

  • milestone set to post-1.0

comment:4 Changed 6 years ago by anonymous

  • milestone post-1.0 deleted

Milestone post-1.0 deleted

comment:5 Changed 4 years ago by lukeplant

  • Severity set to Normal
  • Type set to New feature

comment:6 Changed 4 years ago by melinath

  • 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 Changed 4 years ago by melinath

  • Triage Stage changed from Accepted to Design decision needed

comment:8 Changed 4 years ago by aaugustin

Yes, I also think it's a WONTFIX now that all Django templates use HTML5.

comment:9 Changed 4 years ago by jezdez

  • Resolution set to wontfix
  • Status changed from new to closed

aaugustin is correct.

Note: See TracTickets for help on using tickets.
Back to Top