[wp-trac] Re: [WordPress Trac] #8996: Serve application/xhtml+xml if browser, theme and plugins are compliant

WordPress Trac wp-trac at lists.automattic.com
Thu Jan 29 23:14:58 GMT 2009


#8996: Serve application/xhtml+xml if browser, theme and plugins are compliant
---------------------------+------------------------------------------------
 Reporter:  sampablokuper  |        Owner:  anonymous
     Type:  enhancement    |       Status:  new      
 Priority:  normal         |    Milestone:  2.9      
Component:  Template       |      Version:  2.7      
 Severity:  normal         |   Resolution:           
 Keywords:                 |  
---------------------------+------------------------------------------------
Comment (by sampablokuper):

 Replying to [comment:1 DD32]:
 > All tickets need a milestone.
 Thanks for setting this for me.

 > I am still of the opinion this is a theme-dependant thing, Its not for
 WordPress core to figure out if the theme is compliant and serve.. The
 theme can do that.

 Well, yes, a theme developer should be able to determine (and state) that
 her theme is compliant. But that's not all that's needed; see below.

 > i'd nearly say "Go ahead and put a function which the theme can call to
 register itself as xml-complant", but then, 1 line of code to the theme..
 or 3-5 lines and the theme controls it itself..

 If only the theme needed to be compliant, then you would be correct, but
 as it stands, there is at least some code (a string containing HTML
 entities) in the WP core which is not compliant (for details, see the
 comments in the style.css and functions.php files of the theme I've
 attached to this ticket), and there is also the possibility of plugins
 generating non-compliant code even if the theme and the core files do not.

 So having the option for themes and plugins to register themselves
 compliant might be a good way forward; a bit like the way that themes
 could say they were widget-compatible. This would also simplify handling
 bugs related to compliance: if a theme/plugin that claimed to be compliant
 was found not to be, a bug could be raised against it, etc.

 Of course, for this to work, all core WP files would need to be compliant
 too. Most of them are now, though, so this shouldn't be much work to
 attain.

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


More information about the wp-trac mailing list