[wp-trac] Re: [WordPress Trac] #2141: Serve XHTML properly

[WordPress Trac]

#2141: Serve XHTML properly
--------------------------------------------------------------------------------+
 Reporter:  rolandog                                                            |        Owner:  anonymous
     Type:  enhancement                                                         |       Status:  reopened 
 Priority:  low                                                                 |    Milestone:  2.7      
Component:  Template                                                            |      Version:  2.5      
 Severity:  minor                                                               |   Resolution:           
 Keywords:  xhtml serve properly serving application text html strict template  |  
--------------------------------------------------------------------------------+
Changes (by vlogtheimpaler):

  * status:  closed => reopened
  * severity:  normal => minor
  * priority:  normal => low
  * version:  2.0 => 2.5
  * milestone:  => 2.7
  * keywords:  xhtml serve properly serving application text html strict =>
               xhtml serve properly serving application text
               html strict template
  * resolution:  wontfix =>

Comment:

 I'd like to reopen this with a proposal for solution or some kind of
 middle ground for those who may actually want to serve up true xhtml 1.1
 documents properly within WP. Why not simply have a switch somewhere
 within the options panel for sending valid headers based on the above
 script? As useful as it is, the above "fix" is limited at best within WP
 2.5. And  between views (single entries vs pages) it throws php errors as
 WP appears to write its own in some instances. A fall back or possibly
 even the initial primary option would be to including it as rewrite rules
 to achieve a similar effect.

 Either way, if the user doesn't know what the option does or doesn't want
 to use it then they don't have to. It shouldn't affect them unless they're
 attempting to view tag soup with the wrong headers in which case simple
 documentation could help them before, during or after selecting such an
 option. Either way if they do explore it, it might actually help promote
 true xhtml support and enable other users to actually create well
 formatted code. Any power user versed in xhtml who has or wants to use
 proper xhtml templates could do so just as easily with this.

 To rationalize it a little further - it's pointless, and maybe apathetic
 to wait around because one browser can't get it right. Granted it's a
 major browser, but that doesn't mean others should be held back for it's
 short-comings while other browsers can easily do the same job or even
 more. Making up excuses for themes not supporting it is a very weak at
 best as well, with a few minor tweaks many templates can easily be served
 with the CORRECT headers and others might need a little more work. On that
 end of the spectrum it's neither impossible or mandatory, and as mentioned
 before it may even educate many people in the process.

 In the end, it would shift the burden of proper xhtml support onto the
 browser makers and not because the excuse exists for not enough sites
 serving proper xhtml documents. I don't want to push this as a mandatory
 action to take a stand or anything, but just a power user expecting a
 little more out of a great application with it's own little short-comings.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/2141#comment:4>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software