Ticket #3764 (closed enhancement: invalid)

Opened 2 years ago

Last modified 5 months ago

Selectable Output

Reported by: tandilboy Assigned to: anonymous
Priority: low Milestone:
Component: General Version: 2.2
Severity: normal Keywords:
Cc:

Description

a good idea is add an Output Selector (HTML or XHTML) for better template customization

Change History

02/10/07 22:19:28 changed by JeremyVisser

I'm a little edgy on this one. XHTML is the future of HTML, and is well-supported enough in older browsers; it seems pointless to be to go backwards.

If this were an option, this would be added in the theme code, not as a user-selectable option in the WordPress Administration.

02/11/07 02:18:49 changed by foolswisdom

  • milestone changed from 2.2 to 2.3.

02/13/07 18:54:22 changed by tombarta

If you want to embed MathML or SVG into an XHTML document (at least to Firefox), you have to serve it up with a different Content-Type. Because of the XML parsing, this will break if plugins or themes produce invalid markup. Legacy HTML support (ideally 4.01 strict, but resiliant to errors) should still be provided alongside strict XML support if you really want to get the best of both worlds.

Alternatively, this could be addressed from the other direction by applying something like Tidy to convert malformed markup. Maybe as a user-controlled setting along the lines of: "Force XHTML output? Warning: this may break badly-malformed content." Or as Jeremy says, it could be automated: plugins/themes indicate whether or not they require HTML or XHTML formatting to function, and wordpress core verifies that everything matches.

02/13/07 21:40:09 changed by ryan

By the way, html_type is a hidden option that can be changed to whatever content type you like. 

get_bloginfo('html_type');

09/02/07 19:22:59 changed by foolswisdom

  • milestone changed from 2.3 to 2.5 (future).

06/26/08 10:11:10 changed by pishmishy

  • status changed from new to closed.
  • resolution set to invalid.
  • milestone deleted.

I'm not sure that this is something that'll ever be implemented so closing. I'm pretty sure that everyone accepts that WordPress outputs XHTML and will continue to work this way.

If plugins/themes are producing invalid markup - chase the plugin/theme author :-)